Policies and architecture to dynamically offload vr processing to hmd based on external cues

ABSTRACT

Virtual reality systems and methods are described. For example, one embodiment of an apparatus comprises: a communications interface to provide frame data of a virtual reality scene to a head mounted display (HMD); at least one performance monitor coupled to at least one component of the apparatus the at least one performance monitor to monitor performance of the at least one component and to send an alert based on the performance of the at least one component; a processor to process the frame data; a controller to receive the alert based on the performance of the at least one component and to offload processing of the frame data from the processor to the HMD for processing; and a display to show the rendered view of the scene.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 15/714,936, filed Sep. 25, 2017, which is hereby incorporated by reference.

TECHNICAL FIELD

This invention relates generally to the field of computer processors. More particularly, the invention relates to a virtual reality/augmented reality apparatus and method.

BACKGROUND ART

Virtual reality (VR) refers to data processing technologies that replicate a real or imagined environment by simulating a user's physical presence in that environment and, in some implementations, the user is provided with the ability to interact with the environment. Many current VR environments are displayed either on a computer screen or with a special virtual reality headset. Some simulations include additional sensory information such as sound through speakers or headphones targeted towards VR users.

The VR processing pipeline may involve post processing operations that are not typically performed by 3D graphics applications. For example, these operations may include barrel distortion (BD) correction, asynchronous time warp (ATW), chromatic aberration correction (CAC). These operations can lead to frame drops and latencies which may lead to a poor user experience. Lengthy delays in updating the user's perspective based on head motion can cause simulation sickness, such as headaches, nausea, and dizziness.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:

FIG. 1 is a block diagram of a processing system, according to an embodiment;

FIG. 2 is a block diagram of an embodiment of a processor having one or more processor cores, an integrated memory controller, and an integrated graphics processor;

FIG. 3 is a block diagram of a graphics processor, which may be a discrete graphics processing unit, or may be a graphics processor integrated with a plurality of processing cores;

FIG. 4 is a block diagram of an embodiment of a graphics processing engine for a graphics processor;

FIG. 5 is a block diagram of another embodiment of a graphics processor;

FIGS. 6A-6B illustrate thread execution logic including an array of processing elements employed in a graphics processor;

FIG. 7 is a block diagram illustrating a graphics processor instruction formats;

FIG. 8 is a block diagram of another embodiment of a graphics processor;

FIG. 9A is a block diagram illustrating a graphics processor command format according to an embodiment;

FIG. 9B is a block diagram illustrating a graphics processor command sequence according to an embodiment;

FIG. 10 illustrates exemplary graphics software architecture for a data processing system according to an embodiment;

FIG. 11A is a block diagram illustrating an IP core development system that may be used to manufacture an integrated circuit to perform operations according to an embodiment;

FIG. 11B illustrates a cross-section side view of an integrated circuit package assembly, according to some embodiments;

FIG. 12 is a block diagram illustrating an exemplary system on a chip integrated circuit that may be fabricated using one or more IP cores, according to an embodiment;

FIGS. 13A-13B are block diagrams illustrating exemplary graphics processors for use within an SoC, according to embodiments;

FIGS. 14A-14B illustrate additional exemplary graphics processor logic according to embodiments;

FIGS. 15A-C illustrate different embodiments having multiple graphics engines/pipelines;

FIG. 16 illustrates time warping performed in accordance with one embodiment;

FIG. 17 illustrates one embodiment of an architecture for performing time warping;

FIG. 18 illustrates another embodiment of an architecture for performing time warping;

FIG. 19 illustrates a method in accordance with one embodiment;

FIG. 20 illustrates one embodiment of a time warp apparatus in accordance with one embodiment;

FIGS. 21 and 22 illustrate different sets of execution resources which may be allocated at various stages of the pipeline, in accordance with various embodiments;

FIG. 23 illustrates one embodiment of an architecture for performing offloading of processing to a head mounted display;

FIG. 24 illustrates one embodiment of an architecture for performing offloading of processing to a head mounted display; and

FIG. 25 illustrates a method in accordance to one embodiment.

FIG. 26 illustrates a method in accordance to another embodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments described below. It will be apparent, however, to one skilled in the art that the embodiments may be practiced without some of these specific details. In other instances, well-known structures and devices are shown in block diagram form to avoid obscuring the underlying principles of the embodiments.

Exemplary Graphics Processor Architectures and Data Types

System Overview

FIG. 1 is a block diagram of a processing system 100, according to an embodiment. In various embodiments, the system 100 includes one or more processors 102 and one or more graphics processors 108, and may be a single processor desktop system, a multiprocessor workstation system, or a server system having a large number of processors 102 or processor cores 107. In one embodiment, the system 100 is a processing platform incorporated within a system-on-a-chip (SoC) integrated circuit for use in mobile, handheld, or embedded devices.

In one embodiment the system 100 can include, or be incorporated within a server-based gaming platform, a game console, including a game and media console, a mobile gaming console, a handheld game console, or an online game console. In some embodiments the system 100 is a mobile phone, smart phone, tablet computing device or mobile Internet device. The processing system 100 can also include, couple with, or be integrated within a wearable device, such as a smart watch wearable device, smart eyewear device, augmented reality device, or virtual reality device. In some embodiments, the processing system 100 is a television or set top box device having one or more processors 102 and a graphical interface generated by one or more graphics processors 108.

In some embodiments, the one or more processors 102 each include one or more processor cores 107 to process instructions which, when executed, perform operations for system and user software. In some embodiments, each of the one or more processor cores 107 is configured to process a specific instruction set 109. In some embodiments, instruction set 109 may facilitate Complex Instruction Set Computing (CISC), Reduced Instruction Set Computing (RISC), or computing via a Very Long Instruction Word (VLIW). Multiple processor cores 107 may each process a different instruction set 109, which may include instructions to facilitate the emulation of other instruction sets. Processor core 107 may also include other processing devices, such a Digital Signal Processor (DSP).

In some embodiments, the processor 102 includes cache memory 104. Depending on the architecture, the processor 102 can have a single internal cache or multiple levels of internal cache. In some embodiments, the cache memory is shared among various components of the processor 102. In some embodiments, the processor 102 also uses an external cache (e.g., a Level-3 (L3) cache or Last Level Cache (LLC)) (not shown), which may be shared among processor cores 107 using known cache coherency techniques. A register file 106 is additionally included in processor 102 which may include different types of registers for storing different types of data (e.g., integer registers, floating point registers, status registers, and an instruction pointer register). Some registers may be general-purpose registers, while other registers may be specific to the design of the processor 102.

In some embodiments, one or more processor(s) 102 are coupled with one or more interface bus(es) 110 to transmit communication signals such as address, data, or control signals between processor 102 and other components in the system 100. The interface bus 110, in one embodiment, can be a processor bus, such as a version of the Direct Media Interface (DMI) bus. However, processor busses are not limited to the DMI bus, and may include one or more Peripheral Component Interconnect buses (e.g., PCI, PCI Express), memory busses, or other types of interface busses. In one embodiment the processor(s) 102 include an integrated memory controller 116 and a platform controller hub 130. The memory controller 116 facilitates communication between a memory device and other components of the system 100, while the platform controller hub (PCH) 130 provides connections to I/O devices via a local I/O bus.

The memory device 120 can be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory device, phase-change memory device, or some other memory device having suitable performance to serve as process memory. In one embodiment the memory device 120 can operate as system memory for the system 100, to store data 122 and instructions 121 for use when the one or more processors 102 executes an application or process. Memory controller 116 also couples with an optional external graphics processor 112, which may communicate with the one or more graphics processors 108 in processors 102 to perform graphics and media operations. In some embodiments a display device 111 can connect to the processor(s) 102. The display device 111 can be one or more of an internal display device, as in a mobile electronic device or a laptop device or an external display device attached via a display interface (e.g., DisplayPort, etc.). In one embodiment the display device 111 can be a head mounted display (HMD) such as a stereoscopic display device for use in virtual reality (VR) applications or augmented reality (AR) applications.

In some embodiments the platform controller hub 130 enables peripherals to connect to memory device 120 and processor 102 via a high-speed I/O bus. The I/O peripherals include, but are not limited to, an audio controller 146, a network controller 134, a firmware interface 128, a wireless transceiver 126, touch sensors 125, a data storage device 124 (e.g., hard disk drive, flash memory, etc.). The data storage device 124 can connect via a storage interface (e.g., SATA) or via a peripheral bus, such as a Peripheral Component Interconnect bus (e.g., PCI, PCI Express). The touch sensors 125 can include touch screen sensors, pressure sensors, or fingerprint sensors. The wireless transceiver 126 can be a Wi-Fi transceiver, a Bluetooth transceiver, or a mobile network transceiver such as a 3G, 4G, or Long Term Evolution (LTE) transceiver. The firmware interface 128 enables communication with system firmware, and can be, for example, a unified extensible firmware interface (UEFI). The network controller 134 can enable a network connection to a wired network. In some embodiments, a high-performance network controller (not shown) couples with the interface bus 110. The audio controller 146, in one embodiment, is a multi-channel high definition audio controller. In one embodiment the system 100 includes an optional legacy I/O controller 140 for coupling legacy (e.g., Personal System 2 (PS/2)) devices to the system. The platform controller hub 130 can also connect to one or more Universal Serial Bus (USB) controllers 142 connect input devices, such as keyboard and mouse 143 combinations, a camera 144, or other USB input devices.

It will be appreciated that the system 100 shown is exemplary and not limiting, as other types of data processing systems that are differently configured may also be used. For example, an instance of the memory controller 116 and platform controller hub 130 may be integrated into a discreet external graphics processor, such as the external graphics processor 112. In one embodiment the platform controller hub 130 and/or memory controller 160 may be external to the one or more processor(s) 102. For example, the system 100 can include an external memory controller 116 and platform controller hub 130, which may be configured as a memory controller hub and peripheral controller hub within a system chipset that is in communication with the processor(s) 102.

FIG. 2 is a block diagram of an embodiment of a processor 200 having one or more processor cores 202A-202N, an integrated memory controller 214, and an integrated graphics processor 208. Those elements of FIG. 2 having the same reference numbers (or names) as the elements of any other figure herein can operate or function in any manner similar to that described elsewhere herein, but are not limited to such. Processor 200 can include additional cores up to and including additional core 202N represented by the dashed lined boxes. Each of processor cores 202A-202N includes one or more internal cache units 204A-204N. In some embodiments each processor core also has access to one or more shared cached units 206.

The internal cache units 204A-204N and shared cache units 206 represent a cache memory hierarchy within the processor 200. The cache memory hierarchy may include at least one level of instruction and data cache within each processor core and one or more levels of shared mid-level cache, such as a Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache, where the highest level of cache before external memory is classified as the LLC. In some embodiments, cache coherency logic maintains coherency between the various cache units 206 and 204A-204N.

In some embodiments, processor 200 may also include a set of one or more bus controller units 216 and a system agent core 210. The one or more bus controller units 216 manage a set of peripheral buses, such as one or more PCI or PCI express busses. System agent core 210 provides management functionality for the various processor components. In some embodiments, system agent core 210 includes one or more integrated memory controllers 214 to manage access to various external memory devices (not shown).

In some embodiments, one or more of the processor cores 202A-202N include support for simultaneous multi-threading. In such embodiment, the system agent core 210 includes components for coordinating and operating cores 202A-202N during multi-threaded processing. System agent core 210 may additionally include a power control unit (PCU), which includes logic and components to regulate the power state of processor cores 202A-202N and graphics processor 208.

In some embodiments, processor 200 additionally includes graphics processor 208 to execute graphics processing operations. In some embodiments, the graphics processor 208 couples with the set of shared cache units 206, and the system agent core 210, including the one or more integrated memory controllers 214. In some embodiments, the system agent core 210 also includes a display controller 211 to drive graphics processor output to one or more coupled displays. In some embodiments, display controller 211 may also be a separate module coupled with the graphics processor via at least one interconnect, or may be integrated within the graphics processor 208.

In some embodiments, a ring based interconnect unit 212 is used to couple the internal components of the processor 200. However, an alternative interconnect unit may be used, such as a point-to-point interconnect, a switched interconnect, or other techniques, including techniques well known in the art. In some embodiments, graphics processor 208 couples with the ring interconnect 212 via an I/O link 213.

The exemplary I/O link 213 represents at least one of multiple varieties of I/O interconnects, including an on package I/O interconnect which facilitates communication between various processor components and a high-performance embedded memory module 218, such as an eDRAM module. In some embodiments, each of the processor cores 202A-202N and graphics processor 208 use embedded memory modules 218 as a shared Last Level Cache.

In some embodiments, processor cores 202A-202N are homogenous cores executing the same instruction set architecture. In another embodiment, processor cores 202A-202N are heterogeneous in terms of instruction set architecture (ISA), where one or more of processor cores 202A-202N execute a first instruction set, while at least one of the other cores executes a subset of the first instruction set or a different instruction set. In one embodiment processor cores 202A-202N are heterogeneous in terms of microarchitecture, where one or more cores having a relatively higher power consumption couple with one or more power cores having a lower power consumption. Additionally, processor 200 can be implemented on one or more chips or as an SoC integrated circuit having the illustrated components, in addition to other components.

FIG. 3 is a block diagram of a graphics processor 300, which may be a discrete graphics processing unit, or may be a graphics processor integrated with a plurality of processing cores. In some embodiments, the graphics processor communicates via a memory mapped I/O interface to registers on the graphics processor and with commands placed into the processor memory. In some embodiments, graphics processor 300 includes a memory interface 314 to access memory. Memory interface 314 can be an interface to local memory, one or more internal caches, one or more shared external caches, and/or to system memory.

In some embodiments, graphics processor 300 also includes a display controller 302 to drive display output data to a display device 320. Display controller 302 includes hardware for one or more overlay planes for the display and composition of multiple layers of video or user interface elements. The display device 320 can be an internal or external display device. In one embodiment the display device 320 is a head mounted display device, such as a virtual reality (VR) display device or an augmented reality (AR) display device. In some embodiments, graphics processor 300 includes a video codec engine 306 to encode, decode, or transcode media to, from, or between one or more media encoding formats, including, but not limited to Moving Picture Experts Group (MPEG) formats such as MPEG-2, Advanced Video Coding (AVC) formats such as H.264/MPEG-4 AVC, as well as the Society of Motion Picture & Television Engineers (SMPTE) 421M/VC-1, and Joint Photographic Experts Group (JPEG) formats such as JPEG, and Motion JPEG (MJPEG) formats.

In some embodiments, graphics processor 300 includes a block image transfer (BLIT) engine 304 to perform two-dimensional (2D) rasterizer operations including, for example, bit-boundary block transfers. However, in one embodiment, 2D graphics operations are performed using one or more components of graphics processing engine (GPE) 310. In some embodiments, GPE 310 is a compute engine for performing graphics operations, including three-dimensional (3D) graphics operations and media operations.

In some embodiments, GPE 310 includes a 3D pipeline 312 for performing 3D operations, such as rendering three-dimensional images and scenes using processing functions that act upon 3D primitive shapes (e.g., rectangle, triangle, etc.). The 3D pipeline 312 includes programmable and fixed function elements that perform various tasks within the element and/or spawn execution threads to a 3D/Media sub-system 315. While 3D pipeline 312 can be used to perform media operations, an embodiment of GPE 310 also includes a media pipeline 316 that is specifically used to perform media operations, such as video post-processing and image enhancement.

In some embodiments, media pipeline 316 includes fixed function or programmable logic units to perform one or more specialized media operations, such as video decode acceleration, video de-interlacing, and video encode acceleration in place of, or on behalf of video codec engine 306. In some embodiments, media pipeline 316 additionally includes a thread spawning unit to spawn threads for execution on 3D/Media sub-system 315. The spawned threads perform computations for the media operations on one or more graphics execution units included in 3D/Media sub-system 315.

In some embodiments, 3D/Media subsystem 315 includes logic for executing threads spawned by 3D pipeline 312 and media pipeline 316. In one embodiment, the pipelines send thread execution requests to 3D/Media subsystem 315, which includes thread dispatch logic for arbitrating and dispatching the various requests to available thread execution resources. The execution resources include an array of graphics execution units to process the 3D and media threads. In some embodiments, 3D/Media subsystem 315 includes one or more internal caches for thread instructions and data. In some embodiments, the subsystem also includes shared memory, including registers and addressable memory, to share data between threads and to store output data.

Graphics Processing Engine

FIG. 4 is a block diagram of a graphics processing engine 410 of a graphics processor in accordance with some embodiments. In one embodiment, the graphics processing engine (GPE) 410 is a version of the GPE 310 shown in FIG. 3. Elements of FIG. 4 having the same reference numbers (or names) as the elements of any other figure herein can operate or function in any manner similar to that described elsewhere herein, but are not limited to such. For example, the 3D pipeline 312 and media pipeline 316 of FIG. 3 are illustrated. The media pipeline 316 is optional in some embodiments of the GPE 410 and may not be explicitly included within the GPE 410. For example and in at least one embodiment, a separate media and/or image processor is coupled to the GPE 410.

In some embodiments, GPE 410 couples with or includes a command streamer 403, which provides a command stream to the 3D pipeline 312 and/or media pipelines 316. In some embodiments, command streamer 403 is coupled with memory, which can be system memory, or one or more of internal cache memory and shared cache memory. In some embodiments, command streamer 403 receives commands from the memory and sends the commands to 3D pipeline 312 and/or media pipeline 316. The commands are directives fetched from a ring buffer, which stores commands for the 3D pipeline 312 and media pipeline 316. In one embodiment, the ring buffer can additionally include batch command buffers storing batches of multiple commands. The commands for the 3D pipeline 312 can also include references to data stored in memory, such as but not limited to vertex and geometry data for the 3D pipeline 312 and/or image data and memory objects for the media pipeline 316. The 3D pipeline 312 and media pipeline 316 process the commands and data by performing operations via logic within the respective pipelines or by dispatching one or more execution threads to a graphics core array 414. In one embodiment the graphics core array 414 include one or more blocks of graphics cores (e.g., graphics core(s) 415A, graphics core(s) 415B), each block including one or more graphics cores. Each graphics core includes a set of graphics execution resources that includes general-purpose and graphics specific execution logic to perform graphics and compute operations, as well as fixed function texture processing and/or machine learning and artificial intelligence acceleration logic.

In various embodiments the 3D pipeline 312 includes fixed function and programmable logic to process one or more shader programs, such as vertex shaders, geometry shaders, pixel shaders, fragment shaders, compute shaders, or other shader programs, by processing the instructions and dispatching execution threads to the graphics core array 414. The graphics core array 414 provides a unified block of execution resources for use in processing these shader programs. Multi-purpose execution logic (e.g., execution units) within the graphics core(s) 415A-414B of the graphic core array 414 includes support for various 3D API shader languages and can execute multiple simultaneous execution threads associated with multiple shaders.

In some embodiments the graphics core array 414 also includes execution logic to perform media functions, such as video and/or image processing. In one embodiment, the execution units additionally include general-purpose logic that is programmable to perform parallel general-purpose computational operations, in addition to graphics processing operations. The general-purpose logic can perform processing operations in parallel or in conjunction with general-purpose logic within the processor core(s) 107 of FIG. 1 or core 202A-202N as in FIG. 2.

Output data generated by threads executing on the graphics core array 414 can output data to memory in a unified return buffer (URB) 418. The URB 418 can store data for multiple threads. In some embodiments the URB 418 may be used to send data between different threads executing on the graphics core array 414. In some embodiments the URB 418 may additionally be used for synchronization between threads on the graphics core array and fixed function logic within the shared function logic 420.

In some embodiments, graphics core array 414 is scalable, such that the array includes a variable number of graphics cores, each having a variable number of execution units based on the target power and performance level of GPE 410. In one embodiment the execution resources are dynamically scalable, such that execution resources may be enabled or disabled as needed.

The graphics core array 414 couples with shared function logic 420 that includes multiple resources that are shared between the graphics cores in the graphics core array. The shared functions within the shared function logic 420 are hardware logic units that provide specialized supplemental functionality to the graphics core array 414. In various embodiments, shared function logic 420 includes but is not limited to sampler 421, math 422, and inter-thread communication (ITC) 423 logic. Additionally, some embodiments implement one or more cache(s) 425 within the shared function logic 420.

A shared function is implemented where the demand for a given specialized function is insufficient for inclusion within the graphics core array 414. Instead a single instantiation of that specialized function is implemented as a stand-alone entity in the shared function logic 420 and shared among the execution resources within the graphics core array 414. The precise set of functions that are shared between the graphics core array 414 and included within the graphics core array 414 varies across embodiments. In some embodiments, specific shared functions within the shared function logic 420 that are used extensively by the graphics core array 414 may be included within shared function logic 416 within the graphics core array 414. In various embodiments, the shared function logic 416 within the graphics core array 414 can include some or all logic within the shared function logic 420. In one embodiment, all logic elements within the shared function logic 420 may be duplicated within the shared function logic 416 of the graphics core array 414. In one embodiment the shared function logic 420 is excluded in favor of the shared function logic 416 within the graphics core array 414.

FIG. 5 is a block diagram of hardware logic of a graphics processor core 500, according to some embodiments described herein. Elements of FIG. 5 having the same reference numbers (or names) as the elements of any other figure herein can operate or function in any manner similar to that described elsewhere herein, but are not limited to such. The illustrated graphics processor core 500, in some embodiments, is included within the graphics core array 414 of FIG. 4. The graphics processor core 500, sometimes referred to as a core slice, can be one or multiple graphics cores within a modular graphics processor. The graphics processor core 500 is exemplary of one graphics core slice, and a graphics processor as described herein may include multiple graphics core slices based on target power and performance envelopes. Each graphics core 500 can include a fixed function block 530 coupled with multiple sub-cores 501A-501F, also referred to as sub-slices, that include modular blocks of general-purpose and fixed function logic.

In some embodiments the fixed function block 530 includes a geometry/fixed function pipeline 536 that can be shared by all sub-cores in the graphics processor 500, for example, in lower performance and/or lower power graphics processor implementations. In various embodiments, the geometry/fixed function pipeline 536 includes a 3D fixed function pipeline (e.g., 3D pipeline 312 as in FIG. 3 and FIG. 4) a video front-end unit, a thread spawner and thread dispatcher, and a unified return buffer manager, which manages unified return buffers, such as the unified return buffer 418 of FIG. 4.

In one embodiment the fixed function block 530 also includes a graphics SoC interface 537, a graphics microcontroller 538, and a media pipeline 539. The graphics SoC interface 537 provides an interface between the graphics core 500 and other processor cores within a system on a chip integrated circuit. The graphics microcontroller 538 is a programmable sub-processor that is configurable to manage various functions of the graphics processor 500, including thread dispatch, scheduling, and pre-emption. The media pipeline 539 (e.g., media pipeline 316 of FIG. 3 and FIG. 4) includes logic to facilitate the decoding, encoding, pre-processing, and/or post-processing of multimedia data, including image and video data. The media pipeline 539 implement media operations via requests to compute or sampling logic within the sub-cores 501-501F.

In one embodiment the SoC interface 537 enables the graphics core 500 to communicate with general-purpose application processor cores (e.g., CPUs) and/or other components within an SoC, including memory hierarchy elements such as a shared last level cache memory, the system RAM, and/or embedded on-chip or on-package DRAM. The SoC interface 537 can also enable communication with fixed function devices within the SoC, such as camera imaging pipelines, and enables the use of and/or implements global memory atomics that may be shared between the graphics core 500 and CPUs within the SoC. The SoC interface 537 can also implement power management controls for the graphics core 500 and enable an interface between a clock domain of the graphic core 500 and other clock domains within the SoC. In one embodiment the SoC interface 537 enables receipt of command buffers from a command streamer and global thread dispatcher that are configured to provide commands and instructions to each of one or more graphics cores within a graphics processor. The commands and instructions can be dispatched to the media pipeline 539, when media operations are to be performed, or a geometry and fixed function pipeline (e.g., geometry and fixed function pipeline 536, geometry and fixed function pipeline 514) when graphics processing operations are to be performed.

The graphics microcontroller 538 can be configured to perform various scheduling and management tasks for the graphics core 500. In one embodiment the graphics microcontroller 538 can perform graphics and/or compute workload scheduling on the various graphics parallel engines within execution unit (EU) arrays 502A-502F, 504A-504F within the sub-cores 501A-501F. In this scheduling model, host software executing on a CPU core of an SoC including the graphics core 500 can submit workloads one of multiple graphic processor doorbells, which invokes a scheduling operation on the appropriate graphics engine. Scheduling operations include determining which workload to run next, submitting a workload to a command streamer, pre-empting existing workloads running on an engine, monitoring progress of a workload, and notifying host software when a workload is complete. In one embodiment the graphics microcontroller 538 can also facilitate low-power or idle states for the graphics core 500, providing the graphics core 500 with the ability to save and restore registers within the graphics core 500 across low-power state transitions independently from the operating system and/or graphics driver software on the system.

The graphics core 500 may have greater than or fewer than the illustrated sub-cores 501A-501F, up to N modular sub-cores. For each set of N sub-cores, the graphics core 500 can also include shared function logic 510, shared and/or cache memory 512, a geometry/fixed function pipeline 514, as well as additional fixed function logic 516 to accelerate various graphics and compute processing operations. The shared function logic 510 can include logic units associated with the shared function logic 420 of FIG. 4 (e.g., sampler, math, and/or inter-thread communication logic) that can be shared by each N sub-cores within the graphics core 500. The shared and/or cache memory 512 can be a last-level cache for the set of N sub-cores 501A-501F within the graphics core 500, and can also serve as shared memory that is accessible by multiple sub-cores. The geometry/fixed function pipeline 514 can be included instead of the geometry/fixed function pipeline 536 within the fixed function block 530 and can include the same or similar logic units.

In one embodiment the graphics core 500 includes additional fixed function logic 516 that can include various fixed function acceleration logic for use by the graphics core 500. In one embodiment the additional fixed function logic 516 includes an additional geometry pipeline for use in position only shading. In position-only shading, two geometry pipelines exist, the full geometry pipeline within the geometry/fixed function pipeline 516, 536, and a cull pipeline, which is an additional geometry pipeline which may be included within the additional fixed function logic 516. In one embodiment the cull pipeline is a trimmed down version of the full geometry pipeline. The full pipeline and the cull pipeline can execute different instances of the same application, each instance having a separate context. Position only shading can hide long cull runs of discarded triangles, enabling shading to be completed earlier in some instances. For example and in one embodiment the cull pipeline logic within the additional fixed function logic 516 can execute position shaders in parallel with the main application and generally generates critical results faster than the full pipeline, as the cull pipeline fetches and shades only the position attribute of the vertices, without performing rasterization and rendering of the pixels to the frame buffer. The cull pipeline can use the generated critical results to compute visibility information for all the triangles without regard to whether those triangles are culled. The full pipeline (which in this instance may be referred to as a replay pipeline) can consume the visibility information to skip the culled triangles to shade only the visible triangles that are finally passed to the rasterization phase.

In one embodiment the additional fixed function logic 516 can also include machine-learning acceleration logic, such as fixed function matrix multiplication logic, for implementations including optimizations for machine learning training or inferencing.

Within each graphics sub-core 501A-501F includes a set of execution resources that may be used to perform graphics, media, and compute operations in response to requests by graphics pipeline, media pipeline, or shader programs. The graphics sub-cores 501A-501F include multiple EU arrays 502A-502F, 504A-504F, thread dispatch and inter-thread communication (TD/IC) logic 503A-503F, a 3D (e.g., texture) sampler 505A-505F, a media sampler 506A-506F, a shader processor 507A-507F, and shared local memory (SLM) 508A-508F. The EU arrays 502A-502F, 504A-504F each include multiple execution units, which are general-purpose graphics processing units capable of performing floating-point and integer/fixed-point logic operations in service of a graphics, media, or compute operation, including graphics, media, or compute shader programs. The TD/IC logic 503A-503F performs local thread dispatch and thread control operations for the execution units within a sub-core and facilitate communication between threads executing on the execution units of the sub-core. The 3D sampler 505A-505F can read texture or other 3D graphics related data into memory. The 3D sampler can read texture data differently based on a configured sample state and the texture format associated with a given texture. The media sampler 506A-506F can perform similar read operations based on the type and format associated with media data. In one embodiment, each graphics sub-core 501A-501F can alternately include a unified 3D and media sampler. Threads executing on the execution units within each of the sub-cores 501A-501F can make use of shared local memory 508A-508F within each sub-core, to enable threads executing within a thread group to execute using a common pool of on-chip memory.

Execution Units

FIGS. 6A-6B illustrate thread execution logic 600 including an array of processing elements employed in a graphics processor core according to embodiments described herein. Elements of FIGS. 6A-6B having the same reference numbers (or names) as the elements of any other figure herein can operate or function in any manner similar to that described elsewhere herein, but are not limited to such. FIG. 6A illustrates an overview of thread execution logic 600, which can include a variant of the hardware logic illustrated with each sub-core 501A-501F of FIG. 5. FIG. 6B illustrates exemplary internal details of an execution unit.

As illustrated in FIG. 6A, in some embodiments thread execution logic 600 includes a shader processor 602, a thread dispatcher 604, instruction cache 606, a scalable execution unit array including a plurality of execution units 608A-608N, a sampler 610, a data cache 612, and a data port 614. In one embodiment the scalable execution unit array can dynamically scale by enabling or disabling one or more execution units (e.g., any of execution unit 608A, 608B, 608C, 608D, through 608N−1 and 608N) based on the computational requirements of a workload. In one embodiment the included components are interconnected via an interconnect fabric that links to each of the components. In some embodiments, thread execution logic 600 includes one or more connections to memory, such as system memory or cache memory, through one or more of instruction cache 606, data port 614, sampler 610, and execution units 608A-608N. In some embodiments, each execution unit (e.g. 608A) is a stand-alone programmable general-purpose computational unit that is capable of executing multiple simultaneous hardware threads while processing multiple data elements in parallel for each thread. In various embodiments, the array of execution units 608A-608N is scalable to include any number individual execution units.

In some embodiments, the execution units 608A-608N are primarily used to execute shader programs. A shader processor 602 can process the various shader programs and dispatch execution threads associated with the shader programs via a thread dispatcher 604. In one embodiment the thread dispatcher includes logic to arbitrate thread initiation requests from the graphics and media pipelines and instantiate the requested threads on one or more execution unit in the execution units 608A-608N. For example, a geometry pipeline can dispatch vertex, tessellation, or geometry shaders to the thread execution logic for processing. In some embodiments, thread dispatcher 604 can also process runtime thread spawning requests from the executing shader programs.

In some embodiments, the execution units 608A-608N support an instruction set that includes native support for many standard 3D graphics shader instructions, such that shader programs from graphics libraries (e.g., Direct 3D and OpenGL) are executed with a minimal translation. The execution units support vertex and geometry processing (e.g., vertex programs, geometry programs, vertex shaders), pixel processing (e.g., pixel shaders, fragment shaders) and general-purpose processing (e.g., compute and media shaders). Each of the execution units 608A-608N is capable of multi-issue single instruction multiple data (SIMD) execution and multi-threaded operation enables an efficient execution environment in the face of higher latency memory accesses. Each hardware thread within each execution unit has a dedicated high-bandwidth register file and associated independent thread-state. Execution is multi-issue per clock to pipelines capable of integer, single and double precision floating point operations, SIMD branch capability, logical operations, transcendental operations, and other miscellaneous operations. While waiting for data from memory or one of the shared functions, dependency logic within the execution units 608A-608N causes a waiting thread to sleep until the requested data has been returned. While the waiting thread is sleeping, hardware resources may be devoted to processing other threads. For example, during a delay associated with a vertex shader operation, an execution unit can perform operations for a pixel shader, fragment shader, or another type of shader program, including a different vertex shader.

Each execution unit in execution units 608A-608N operates on arrays of data elements. The number of data elements is the “execution size,” or the number of channels for the instruction. An execution channel is a logical unit of execution for data element access, masking, and flow control within instructions. The number of channels may be independent of the number of physical Arithmetic Logic Units (ALUs) or Floating Point Units (FPUs) for a particular graphics processor. In some embodiments, execution units 608A-608N support integer and floating-point data types.

The execution unit instruction set includes SIMD instructions. The various data elements can be stored as a packed data type in a register and the execution unit will process the various elements based on the data size of the elements. For example, when operating on a 256-bit wide vector, the 256 bits of the vector are stored in a register and the execution unit operates on the vector as four separate 64-bit packed data elements (Quad-Word (QW) size data elements), eight separate 32-bit packed data elements (Double Word (DW) size data elements), sixteen separate 16-bit packed data elements (Word (W) size data elements), or thirty-two separate 8-bit data elements (byte (B) size data elements). However, different vector widths and register sizes are possible.

In one embodiment one or more execution units can be combined into a fused execution unit 609A-609N having thread control logic (607A-607N) that is common to the fused EUs. Multiple EUs can be fused into an EU group. Each EU in the fused EU group can be configured to execute a separate SIMD hardware thread. The number of EUs in a fused EU group can vary according to embodiments. Additionally, various SIMD widths can be performed per-EU, including but not limited to SIMD8, SIMD16, and SIMD32. Each fused graphics execution unit 609A-609N includes at least two execution units. For example, fused execution unit 609A includes a first EU 608A, second EU 608B, and thread control logic 607A that is common to the first EU 608A and the second EU 608B. The thread control logic 607A controls threads executed on the fused graphics execution unit 609A, allowing each EU within the fused execution units 609A-609N to execute using a common instruction pointer register.

One or more internal instruction caches (e.g., 606) are included in the thread execution logic 600 to cache thread instructions for the execution units. In some embodiments, one or more data caches (e.g., 612) are included to cache thread data during thread execution. In some embodiments, a sampler 610 is included to provide texture sampling for 3D operations and media sampling for media operations. In some embodiments, sampler 610 includes specialized texture or media sampling functionality to process texture or media data during the sampling process before providing the sampled data to an execution unit.

During execution, the graphics and media pipelines send thread initiation requests to thread execution logic 600 via thread spawning and dispatch logic. Once a group of geometric objects has been processed and rasterized into pixel data, pixel processor logic (e.g., pixel shader logic, fragment shader logic, etc.) within the shader processor 602 is invoked to further compute output information and cause results to be written to output surfaces (e.g., color buffers, depth buffers, stencil buffers, etc.). In some embodiments, a pixel shader or fragment shader calculates the values of the various vertex attributes that are to be interpolated across the rasterized object. In some embodiments, pixel processor logic within the shader processor 602 then executes an application programming interface (API)-supplied pixel or fragment shader program. To execute the shader program, the shader processor 602 dispatches threads to an execution unit (e.g., 608A) via thread dispatcher 604. In some embodiments, shader processor 602 uses texture sampling logic in the sampler 610 to access texture data in texture maps stored in memory. Arithmetic operations on the texture data and the input geometry data compute pixel color data for each geometric fragment, or discards one or more pixels from further processing.

In some embodiments, the data port 614 provides a memory access mechanism for the thread execution logic 600 to output processed data to memory for further processing on a graphics processor output pipeline. In some embodiments, the data port 614 includes or couples to one or more cache memories (e.g., data cache 612) to cache data for memory access via the data port.

As illustrated in FIG. 6B, a graphics execution unit 608 can include an instruction fetch unit 637, a general register file array (GRF) 624, an architectural register file array (ARF) 626, a thread arbiter 622, a send unit 630, a branch unit 632, a set of SIMD floating point units (FPUs) 634, and in one embodiment a set of dedicated integer SIMD ALUs 635. The GRF 624 and ARF 626 includes the set of general register files and architecture register files associated with each simultaneous hardware thread that may be active in the graphics execution unit 608. In one embodiment, per thread architectural state is maintained in the ARF 626, while data used during thread execution is stored in the GRF 624. The execution state of each thread, including the instruction pointers for each thread, can be held in thread-specific registers in the ARF 626.

In one embodiment the graphics execution unit 608 has an architecture that is a combination of Simultaneous Multi-Threading (SMT) and fine-grained Interleaved Multi-Threading (IMT). The architecture has a modular configuration that can be fine tuned at design time based on a target number of simultaneous threads and number of registers per execution unit, where execution unit resources are divided across logic used to execute multiple simultaneous threads.

In one embodiment, the graphics execution unit 608 can co-issue multiple instructions, which may each be different instructions. The thread arbiter 622 of the graphics execution unit thread 608 can dispatch the instructions to one of the send unit 630, branch unit 642, or SIMD FPU(s) 634 for execution. Each execution thread can access 128 general-purpose registers within the GRF 624, where each register can store 32 bytes, accessible as a SIMD 8-element vector of 32-bit data elements. In one embodiment, each execution unit thread has access to 4 Kbytes within the GRF 624, although embodiments are not so limited, and greater or fewer register resources may be provided in other embodiments. In one embodiment up to seven threads can execute simultaneously, although the number of threads per execution unit can also vary according to embodiments. In an embodiment in which seven threads may access 4 Kbytes, the GRF 624 can store a total of 28 Kbytes. Flexible addressing modes can permit registers to be addressed together to build effectively wider registers or to represent strided rectangular block data structures.

In one embodiment, memory operations, sampler operations, and other longer-latency system communications are dispatched via “send” instructions that are executed by the message passing send unit 630. In one embodiment, branch instructions are dispatched to a dedicated branch unit 632 to facilitate SIMD divergence and eventual convergence.

In one embodiment the graphics execution unit 608 includes one or more SIMD floating point units (FPU(s)) 634 to perform floating-point operations. In one embodiment, the FPU(s) 634 also support integer computation. In one embodiment the FPU(s) 634 can SIMD execute up to M number of 32-bit floating-point (or integer) operations, or SIMD execute up to 2M 16-bit integer or 16-bit floating-point operations. In one embodiment, at least one of the FPU(s) provides extended math capability to support high-throughput transcendental math functions and double precision 64-bit floating-point. In some embodiments, a set of 8-bit integer SIMD ALUs 635 are also present, and may be specifically optimized to perform operations associated with machine learning computations.

In one embodiment, arrays of multiple instances of the graphics execution unit 608 can be instantiated in a graphics sub-core grouping (e.g., a sub-slice). For scalability, product architects can chose the exact number of execution units per sub-core grouping. In one embodiment the execution unit 608 can execute instructions across a plurality of execution channels. In a further embodiment, each thread executed on the graphics execution unit 608 is executed on a different channel.

FIG. 7 is a block diagram illustrating a graphics processor instruction formats 700 according to some embodiments. In one or more embodiment, the graphics processor execution units support an instruction set having instructions in multiple formats. The solid lined boxes illustrate the components that are generally included in an execution unit instruction, while the dashed lines include components that are optional or that are only included in a sub-set of the instructions. In some embodiments, instruction format 700 described and illustrated are macro-instructions, in that they are instructions supplied to the execution unit, as opposed to micro-operations resulting from instruction decode once the instruction is processed.

In some embodiments, the graphics processor execution units natively support instructions in a 128-bit instruction format 710. A 64-bit compacted instruction format 730 is available for some instructions based on the selected instruction, instruction options, and number of operands. The native 128-bit instruction format 710 provides access to all instruction options, while some options and operations are restricted in the 64-bit format 730. The native instructions available in the 64-bit format 730 vary by embodiment. In some embodiments, the instruction is compacted in part using a set of index values in an index field 713. The execution unit hardware references a set of compaction tables based on the index values and uses the compaction table outputs to reconstruct a native instruction in the 128-bit instruction format 710.

For each format, instruction opcode 712 defines the operation that the execution unit is to perform. The execution units execute each instruction in parallel across the multiple data elements of each operand. For example, in response to an add instruction the execution unit performs a simultaneous add operation across each color channel representing a texture element or picture element. By default, the execution unit performs each instruction across all data channels of the operands. In some embodiments, instruction control field 714 enables control over certain execution options, such as channels selection (e.g., predication) and data channel order (e.g., swizzle). For instructions in the 128-bit instruction format 710 an exec-size field 716 limits the number of data channels that will be executed in parallel. In some embodiments, exec-size field 716 is not available for use in the 64-bit compact instruction format 730.

Some execution unit instructions have up to three operands including two source operands, src0 720, src1 722, and one destination 718. In some embodiments, the execution units support dual destination instructions, where one of the destinations is implied. Data manipulation instructions can have a third source operand (e.g., SRC2 724), where the instruction opcode 712 determines the number of source operands. An instruction's last source operand can be an immediate (e.g., hard-coded) value passed with the instruction.

In some embodiments, the 128-bit instruction format 710 includes an access/address mode field 726 specifying, for example, whether direct register addressing mode or indirect register addressing mode is used. When direct register addressing mode is used, the register address of one or more operands is directly provided by bits in the instruction.

In some embodiments, the 128-bit instruction format 710 includes an access/address mode field 726, which specifies an address mode and/or an access mode for the instruction. In one embodiment the access mode is used to define a data access alignment for the instruction. Some embodiments support access modes including a 16-byte aligned access mode and a 1-byte aligned access mode, where the byte alignment of the access mode determines the access alignment of the instruction operands. For example, when in a first mode, the instruction may use byte-aligned addressing for source and destination operands and when in a second mode, the instruction may use 16-byte-aligned addressing for all source and destination operands.

In one embodiment, the address mode portion of the access/address mode field 726 determines whether the instruction is to use direct or indirect addressing. When direct register addressing mode is used bits in the instruction directly provide the register address of one or more operands. When indirect register addressing mode is used, the register address of one or more operands may be computed based on an address register value and an address immediate field in the instruction.

In some embodiments instructions are grouped based on opcode 712 bit-fields to simplify Opcode decode 740. For an 8-bit opcode, bits 4, 5, and 6 allow the execution unit to determine the type of opcode. The precise opcode grouping shown is merely an example. In some embodiments, a move and logic opcode group 742 includes data movement and logic instructions (e.g., move (mov), compare (cmp)). In some embodiments, move and logic group 742 shares the five most significant bits (MSB), where move (mov) instructions are in the form of 0000xxxxb and logic instructions are in the form of 0001xxxxb. A flow control instruction group 744 (e.g., call, jump (jmp)) includes instructions in the form of 0010xxxxb (e.g., 0x20). A miscellaneous instruction group 746 includes a mix of instructions, including synchronization instructions (e.g., wait, send) in the form of 0011xxxxb (e.g., 0x30). A parallel math instruction group 748 includes component-wise arithmetic instructions (e.g., add, multiply (mul)) in the form of 0100xxxxb (e.g., 0x40). The parallel math group 748 performs the arithmetic operations in parallel across data channels. The vector math group 750 includes arithmetic instructions (e.g., dp4) in the form of 0101xxxxb (e.g., 0x50). The vector math group performs arithmetic such as dot product calculations on vector operands.

Graphics Pipeline

FIG. 8 is a block diagram of another embodiment of a graphics processor 800. Elements of FIG. 8 having the same reference numbers (or names) as the elements of any other figure herein can operate or function in any manner similar to that described elsewhere herein, but are not limited to such.

In some embodiments, graphics processor 800 includes a geometry pipeline 820, a media pipeline 830, a display engine 840, thread execution logic 850, and a render output pipeline 870. In some embodiments, graphics processor 800 is a graphics processor within a multi-core processing system that includes one or more general-purpose processing cores. The graphics processor is controlled by register writes to one or more control registers (not shown) or via commands issued to graphics processor 800 via a ring interconnect 802. In some embodiments, ring interconnect 802 couples graphics processor 800 to other processing components, such as other graphics processors or general-purpose processors. Commands from ring interconnect 802 are interpreted by a command streamer 803, which supplies instructions to individual components of the geometry pipeline 820 or the media pipeline 830.

In some embodiments, command streamer 803 directs the operation of a vertex fetcher 805 that reads vertex data from memory and executes vertex-processing commands provided by command streamer 803. In some embodiments, vertex fetcher 805 provides vertex data to a vertex shader 807, which performs coordinate space transformation and lighting operations to each vertex. In some embodiments, vertex fetcher 805 and vertex shader 807 execute vertex-processing instructions by dispatching execution threads to execution units 852A-852B via a thread dispatcher 831.

In some embodiments, execution units 852A-852B are an array of vector processors having an instruction set for performing graphics and media operations. In some embodiments, execution units 852A-852B have an attached L1 cache 851 that is specific for each array or shared between the arrays. The cache can be configured as a data cache, an instruction cache, or a single cache that is partitioned to contain data and instructions in different partitions.

In some embodiments, geometry pipeline 820 includes tessellation components to perform hardware-accelerated tessellation of 3D objects. In some embodiments, a programmable hull shader 811 configures the tessellation operations. A programmable domain shader 817 provides back-end evaluation of tessellation output. A tessellator 813 operates at the direction of hull shader 811 and contains special purpose logic to generate a set of detailed geometric objects based on a coarse geometric model that is provided as input to geometry pipeline 820. In some embodiments, if tessellation is not used, tessellation components (e.g., hull shader 811, tessellator 813, and domain shader 817) can be bypassed.

In some embodiments, complete geometric objects can be processed by a geometry shader 819 via one or more threads dispatched to execution units 852A-852B, or can proceed directly to the clipper 829. In some embodiments, the geometry shader operates on entire geometric objects, rather than vertices or patches of vertices as in previous stages of the graphics pipeline. If the tessellation is disabled the geometry shader 819 receives input from the vertex shader 807. In some embodiments, geometry shader 819 is programmable by a geometry shader program to perform geometry tessellation if the tessellation units are disabled.

Before rasterization, a clipper 829 processes vertex data. The clipper 829 may be a fixed function clipper or a programmable clipper having clipping and geometry shader functions. In some embodiments, a rasterizer and depth test component 873 in the render output pipeline 870 dispatches pixel shaders to convert the geometric objects into per pixel representations. In some embodiments, pixel shader logic is included in thread execution logic 850. In some embodiments, an application can bypass the rasterizer and depth test component 873 and access un-rasterized vertex data via a stream out unit 823.

The graphics processor 800 has an interconnect bus, interconnect fabric, or some other interconnect mechanism that allows data and message passing amongst the major components of the processor. In some embodiments, execution units 852A-852B and associated logic units (e.g., L1 cache 851, sampler 854, texture cache 858, etc.) interconnect via a data port 856 to perform memory access and communicate with render output pipeline components of the processor. In some embodiments, sampler 854, caches 851, 858 and execution units 852A-852B each have separate memory access paths. In one embodiment the texture cache 858 can also be configured as a sampler cache.

In some embodiments, render output pipeline 870 contains a rasterizer and depth test component 873 that converts vertex-based objects into an associated pixel-based representation. In some embodiments, the rasterizer logic includes a windower/masker unit to perform fixed function triangle and line rasterization. An associated render cache 878 and depth cache 879 are also available in some embodiments. A pixel operations component 877 performs pixel-based operations on the data, though in some instances, pixel operations associated with 2D operations (e.g. bit block image transfers with blending) are performed by the 2D engine 841, or substituted at display time by the display controller 843 using overlay display planes. In some embodiments, a shared L3 cache 875 is available to all graphics components, allowing the sharing of data without the use of main system memory.

In some embodiments, graphics processor media pipeline 830 includes a media engine 837 and a video front-end 834. In some embodiments, video front-end 834 receives pipeline commands from the command streamer 803. In some embodiments, media pipeline 830 includes a separate command streamer. In some embodiments, video front-end 834 processes media commands before sending the command to the media engine 837. In some embodiments, media engine 837 includes thread spawning functionality to spawn threads for dispatch to thread execution logic 850 via thread dispatcher 831.

In some embodiments, graphics processor 800 includes a display engine 840. In some embodiments, display engine 840 is external to processor 800 and couples with the graphics processor via the ring interconnect 802, or some other interconnect bus or fabric. In some embodiments, display engine 840 includes a 2D engine 841 and a display controller 843. In some embodiments, display engine 840 contains special purpose logic capable of operating independently of the 3D pipeline. In some embodiments, display controller 843 couples with a display device (not shown), which may be a system integrated display device, as in a laptop computer, or an external display device attached via a display device connector.

In some embodiments, the geometry pipeline 820 and media pipeline 830 are configurable to perform operations based on multiple graphics and media programming interfaces and are not specific to any one application programming interface (API). In some embodiments, driver software for the graphics processor translates API calls that are specific to a particular graphics or media library into commands that can be processed by the graphics processor. In some embodiments, support is provided for the Open Graphics Library (OpenGL), Open Computing Language (OpenCL), and/or Vulkan graphics and compute API, all from the Khronos Group. In some embodiments, support may also be provided for the Direct3D library from the Microsoft Corporation. In some embodiments, a combination of these libraries may be supported. Support may also be provided for the Open Source Computer Vision Library (OpenCV). A future API with a compatible 3D pipeline would also be supported if a mapping can be made from the pipeline of the future API to the pipeline of the graphics processor.

Graphics Pipeline Programming

FIG. 9A is a block diagram illustrating a graphics processor command format 900 according to some embodiments. FIG. 9B is a block diagram illustrating a graphics processor command sequence 910 according to an embodiment. The solid lined boxes in FIG. 9A illustrate the components that are generally included in a graphics command while the dashed lines include components that are optional or that are only included in a sub-set of the graphics commands. The exemplary graphics processor command format 900 of FIG. 9A includes data fields to identify a client 902, a command operation code (opcode) 904, and data 906 for the command A sub-opcode 905 and a command size 908 are also included in some commands.

In some embodiments, client 902 specifies the client unit of the graphics device that processes the command data. In some embodiments, a graphics processor command parser examines the client field of each command to condition the further processing of the command and route the command data to the appropriate client unit. In some embodiments, the graphics processor client units include a memory interface unit, a render unit, a 2D unit, a 3D unit, and a media unit. Each client unit has a corresponding processing pipeline that processes the commands Once the command is received by the client unit, the client unit reads the opcode 904 and, if present, sub-opcode 905 to determine the operation to perform. The client unit performs the command using information in data field 906. For some commands an explicit command size 908 is expected to specify the size of the command. In some embodiments, the command parser automatically determines the size of at least some of the commands based on the command opcode. In some embodiments commands are aligned via multiples of a double word.

The flow diagram in FIG. 9B illustrates an exemplary graphics processor command sequence 910. In some embodiments, software or firmware of a data processing system that features an embodiment of a graphics processor uses a version of the command sequence shown to set up, execute, and terminate a set of graphics operations. A sample command sequence is shown and described for purposes of example only as embodiments are not limited to these specific commands or to this command sequence. Moreover, the commands may be issued as batch of commands in a command sequence, such that the graphics processor will process the sequence of commands in at least partially concurrence.

In some embodiments, the graphics processor command sequence 910 may begin with a pipeline flush command 912 to cause any active graphics pipeline to complete the currently pending commands for the pipeline. In some embodiments, the 3D pipeline 922 and the media pipeline 924 do not operate concurrently. The pipeline flush is performed to cause the active graphics pipeline to complete any pending commands In response to a pipeline flush, the command parser for the graphics processor will pause command processing until the active drawing engines complete pending operations and the relevant read caches are invalidated. Optionally, any data in the render cache that is marked ‘dirty’ can be flushed to memory. In some embodiments, pipeline flush command 912 can be used for pipeline synchronization or before placing the graphics processor into a low power state.

In some embodiments, a pipeline select command 913 is used when a command sequence requires the graphics processor to explicitly switch between pipelines. In some embodiments, a pipeline select command 913 is required only once within an execution context before issuing pipeline commands unless the context is to issue commands for both pipelines. In some embodiments, a pipeline flush command 912 is required immediately before a pipeline switch via the pipeline select command 913.

In some embodiments, a pipeline control command 914 configures a graphics pipeline for operation and is used to program the 3D pipeline 922 and the media pipeline 924. In some embodiments, pipeline control command 914 configures the pipeline state for the active pipeline. In one embodiment, the pipeline control command 914 is used for pipeline synchronization and to clear data from one or more cache memories within the active pipeline before processing a batch of commands.

In some embodiments, return buffer state commands 916 are used to configure a set of return buffers for the respective pipelines to write data. Some pipeline operations require the allocation, selection, or configuration of one or more return buffers into which the operations write intermediate data during processing. In some embodiments, the graphics processor also uses one or more return buffers to store output data and to perform cross thread communication. In some embodiments, the return buffer state 916 includes selecting the size and number of return buffers to use for a set of pipeline operations.

The remaining commands in the command sequence differ based on the active pipeline for operations. Based on a pipeline determination 920, the command sequence is tailored to the 3D pipeline 922 beginning with the 3D pipeline state 930 or the media pipeline 924 beginning at the media pipeline state 940.

The commands to configure the 3D pipeline state 930 include 3D state setting commands for vertex buffer state, vertex element state, constant color state, depth buffer state, and other state variables that are to be configured before 3D primitive commands are processed. The values of these commands are determined at least in part based on the particular 3D API in use. In some embodiments, 3D pipeline state 930 commands are also able to selectively disable or bypass certain pipeline elements if those elements will not be used.

In some embodiments, 3D primitive 932 command is used to submit 3D primitives to be processed by the 3D pipeline. Commands and associated parameters that are passed to the graphics processor via the 3D primitive 932 command are forwarded to the vertex fetch function in the graphics pipeline. The vertex fetch function uses the 3D primitive 932 command data to generate vertex data structures. The vertex data structures are stored in one or more return buffers. In some embodiments, 3D primitive 932 command is used to perform vertex operations on 3D primitives via vertex shaders. To process vertex shaders, 3D pipeline 922 dispatches shader execution threads to graphics processor execution units.

In some embodiments, 3D pipeline 922 is triggered via an execute 934 command or event. In some embodiments, a register write triggers command execution. In some embodiments execution is triggered via a ‘go’ or ‘kick’ command in the command sequence. In one embodiment, command execution is triggered using a pipeline synchronization command to flush the command sequence through the graphics pipeline. The 3D pipeline will perform geometry processing for the 3D primitives. Once operations are complete, the resulting geometric objects are rasterized and the pixel engine colors the resulting pixels. Additional commands to control pixel shading and pixel back end operations may also be included for those operations.

In some embodiments, the graphics processor command sequence 910 follows the media pipeline 924 path when performing media operations. In general, the specific use and manner of programming for the media pipeline 924 depends on the media or compute operations to be performed. Specific media decode operations may be offloaded to the media pipeline during media decode. In some embodiments, the media pipeline can also be bypassed and media decode can be performed in whole or in part using resources provided by one or more general-purpose processing cores. In one embodiment, the media pipeline also includes elements for general-purpose graphics processor unit (GPGPU) operations, where the graphics processor is used to perform SIMD vector operations using computational shader programs that are not explicitly related to the rendering of graphics primitives.

In some embodiments, media pipeline 924 is configured in a similar manner as the 3D pipeline 922. A set of commands to configure the media pipeline state 940 are dispatched or placed into a command queue before the media object commands 942. In some embodiments, commands for the media pipeline state 940 include data to configure the media pipeline elements that will be used to process the media objects. This includes data to configure the video decode and video encode logic within the media pipeline, such as encode or decode format. In some embodiments, commands for the media pipeline state 940 also support the use of one or more pointers to “indirect” state elements that contain a batch of state settings.

In some embodiments, media object commands 942 supply pointers to media objects for processing by the media pipeline. The media objects include memory buffers containing video data to be processed. In some embodiments, all media pipeline states must be valid before issuing a media object command 942. Once the pipeline state is configured and media object commands 942 are queued, the media pipeline 924 is triggered via an execute command 944 or an equivalent execute event (e.g., register write). Output from media pipeline 924 may then be post processed by operations provided by the 3D pipeline 922 or the media pipeline 924. In some embodiments, GPGPU operations are configured and executed in a similar manner as media operations.

Graphics Software Architecture

FIG. 10 illustrates exemplary graphics software architecture for a data processing system 1000 according to some embodiments. In some embodiments, software architecture includes a 3D graphics application 1010, an operating system 1020, and at least one processor 1030. In some embodiments, processor 1030 includes a graphics processor 1032 and one or more general-purpose processor core(s) 1034. The graphics application 1010 and operating system 1020 each execute in the system memory 1050 of the data processing system.

In some embodiments, 3D graphics application 1010 contains one or more shader programs including shader instructions 1012. The shader language instructions may be in a high-level shader language, such as the High Level Shader Language (HLSL) or the OpenGL Shader Language (GLSL). The application also includes executable instructions 1014 in a machine language suitable for execution by the general-purpose processor core 1034. The application also includes graphics objects 1016 defined by vertex data.

In some embodiments, operating system 1020 is a Microsoft® Windows® operating system from the Microsoft Corporation, a proprietary UNIX-like operating system, or an open source UNIX-like operating system using a variant of the Linux kernel. The operating system 1020 can support a graphics API 1022 such as the Direct3D API, the OpenGL API, or the Vulkan API. When the Direct3D API is in use, the operating system 1020 uses a front-end shader compiler 1024 to compile any shader instructions 1012 in HLSL into a lower-level shader language. The compilation may be a just-in-time (JIT) compilation or the application can perform shader pre-compilation. In some embodiments, high-level shaders are compiled into low-level shaders during the compilation of the 3D graphics application 1010. In some embodiments, the shader instructions 1012 are provided in an intermediate form, such as a version of the Standard Portable Intermediate Representation (SPIR) used by the Vulkan API.

In some embodiments, user mode graphics driver 1026 contains a back-end shader compiler 1027 to convert the shader instructions 1012 into a hardware specific representation. When the OpenGL API is in use, shader instructions 1012 in the GLSL high-level language are passed to a user mode graphics driver 1026 for compilation. In some embodiments, user mode graphics driver 1026 uses operating system kernel mode functions 1028 to communicate with a kernel mode graphics driver 1029. In some embodiments, kernel mode graphics driver 1029 communicates with graphics processor 1032 to dispatch commands and instructions.

IP Core Implementations

One or more aspects of at least one embodiment may be implemented by representative code stored on a machine-readable medium which represents and/or defines logic within an integrated circuit such as a processor. For example, the machine-readable medium may include instructions which represent various logic within the processor. When read by a machine, the instructions may cause the machine to fabricate the logic to perform the techniques described herein. Such representations, known as “IP cores,” are reusable units of logic for an integrated circuit that may be stored on a tangible, machine-readable medium as a hardware model that describes the structure of the integrated circuit. The hardware model may be supplied to various customers or manufacturing facilities, which load the hardware model on fabrication machines that manufacture the integrated circuit. The integrated circuit may be fabricated such that the circuit performs operations described in association with any of the embodiments described herein.

FIG. 11A is a block diagram illustrating an IP core development system 1100 that may be used to manufacture an integrated circuit to perform operations according to an embodiment. The IP core development system 1100 may be used to generate modular, re-usable designs that can be incorporated into a larger design or used to construct an entire integrated circuit (e.g., an SOC integrated circuit). A design facility 1130 can generate a software simulation 1110 of an IP core design in a high-level programming language (e.g., C/C++). The software simulation 1110 can be used to design, test, and verify the behavior of the IP core using a simulation model 1112. The simulation model 1112 may include functional, behavioral, and/or timing simulations. A register transfer level (RTL) design 1115 can then be created or synthesized from the simulation model 1112. The RTL design 1115 is an abstraction of the behavior of the integrated circuit that models the flow of digital signals between hardware registers, including the associated logic performed using the modeled digital signals. In addition to an RTL design 1115, lower-level designs at the logic level or transistor level may also be created, designed, or synthesized. Thus, the particular details of the initial design and simulation may vary.

The RTL design 1115 or equivalent may be further synthesized by the design facility into a hardware model 1120, which may be in a hardware description language (HDL), or some other representation of physical design data. The HDL may be further simulated or tested to verify the IP core design. The IP core design can be stored for delivery to a 3^(rd) party fabrication facility 1165 using non-volatile memory 1140 (e.g., hard disk, flash memory, or any non-volatile storage medium). Alternatively, the IP core design may be transmitted (e.g., via the Internet) over a wired connection 1150 or wireless connection 1160. The fabrication facility 1165 may then fabricate an integrated circuit that is based at least in part on the IP core design. The fabricated integrated circuit can be configured to perform operations in accordance with at least one embodiment described herein.

FIG. 11B illustrates a cross-section side view of an integrated circuit package assembly 1170, according to some embodiments described herein. The integrated circuit package assembly 1170 illustrates an implementation of one or more processor or accelerator devices as described herein. The package assembly 1170 includes multiple units of hardware logic 1172, 1174 connected to a substrate 1180. The logic 1172, 1174 may be implemented at least partly in configurable logic or fixed-functionality logic hardware, and can include one or more portions of any of the processor core(s), graphics processor(s), or other accelerator devices described herein. Each unit of logic 1172, 1174 can be implemented within a semiconductor die and coupled with the substrate 1180 via an interconnect structure 1173. The interconnect structure 1173 may be configured to route electrical signals between the logic 1172, 1174 and the substrate 1180, and can include interconnects such as, but not limited to bumps or pillars. In some embodiments, the interconnect structure 1173 may be configured to route electrical signals such as, for example, input/output (I/O) signals and/or power or ground signals associated with the operation of the logic 1172, 1174. In some embodiments, the substrate 1180 is an epoxy-based laminate substrate. The package substrate 1180 may include other suitable types of substrates in other embodiments. The package assembly 1170 can be connected to other electrical devices via a package interconnect 1183. The package interconnect 1183 may be coupled to a surface of the substrate 1180 to route electrical signals to other electrical devices, such as a motherboard, other chipset, or multi-chip module.

In some embodiments, the units of logic 1172, 1174 are electrically coupled with a bridge 1182 that is configured to route electrical signals between the logic 1172, 1174. The bridge 1182 may be a dense interconnect structure that provides a route for electrical signals. The bridge 1182 may include a bridge substrate composed of glass or a suitable semiconductor material. Electrical routing features can be formed on the bridge substrate to provide a chip-to-chip connection between the logic 1172, 1174.

Although two units of logic 1172, 1174 and a bridge 1182 are illustrated, embodiments described herein may include more or fewer logic units on one or more dies. The one or more dies may be connected by zero or more bridges, as the bridge 1182 may be excluded when the logic is included on a single die. Alternatively, multiple dies or units of logic can be connected by one or more bridges. Additionally, multiple logic units, dies, and bridges can be connected together in other possible configurations, including three-dimensional configurations.

Exemplary System on a Chip Integrated Circuit

FIGS. 12-14 illustrated exemplary integrated circuits and associated graphics processors that may be fabricated using one or more IP cores, according to various embodiments described herein. In addition to what is illustrated, other logic and circuits may be included, including additional graphics processors/cores, peripheral interface controllers, or general-purpose processor cores.

FIG. 12 is a block diagram illustrating an exemplary system on a chip integrated circuit 1200 that may be fabricated using one or more IP cores, according to an embodiment. Exemplary integrated circuit 1200 includes one or more application processor(s) 1205 (e.g., CPUs), at least one graphics processor 1210, and may additionally include an image processor 1215 and/or a video processor 1220, any of which may be a modular IP core from the same or multiple different design facilities. Integrated circuit 1200 includes peripheral or bus logic including a USB controller 1225, UART controller 1230, an SPI/SDIO controller 1235, and an I²S/I²C controller 1240. Additionally, the integrated circuit can include a display device 1245 coupled to one or more of a high-definition multimedia interface (HDMI) controller 1250 and a mobile industry processor interface (MIPI) display interface 1255. Storage may be provided by a flash memory subsystem 1260 including flash memory and a flash memory controller. Memory interface may be provided via a memory controller 1265 for access to SDRAM or SRAM memory devices. Some integrated circuits additionally include an embedded security engine 1270.

FIGS. 13A-13B are block diagrams illustrating exemplary graphics processors for use within an SoC, according to embodiments described herein. FIG. 13A illustrates an exemplary graphics processor 1310 of a system on a chip integrated circuit that may be fabricated using one or more IP cores, according to an embodiment. FIG. 13B illustrates an additional exemplary graphics processor 1340 of a system on a chip integrated circuit that may be fabricated using one or more IP cores, according to an embodiment. Graphics processor 1310 of FIG. 13A is an example of a low power graphics processor core. Graphics processor 1340 of FIG. 13B is an example of a higher performance graphics processor core. Each of the graphics processors 1310, 1340 can be variants of the graphics processor 1210 of FIG. 12.

As shown in FIG. 13A, graphics processor 1310 includes a vertex processor 1305 and one or more fragment processor(s) 1315A-1315N (e.g., 1315A, 1315B, 1315C, 1315D, through 1315N−1, and 1315N). Graphics processor 1310 can execute different shader programs via separate logic, such that the vertex processor 1305 is optimized to execute operations for vertex shader programs, while the one or more fragment processor(s) 1315A-1315N execute fragment (e.g., pixel) shading operations for fragment or pixel shader programs. The vertex processor 1305 performs the vertex processing stage of the 3D graphics pipeline and generates primitives and vertex data. The fragment processor(s) 1315A-1315N use the primitive and vertex data generated by the vertex processor 1305 to produce a framebuffer that is displayed on a display device. In one embodiment, the fragment processor(s) 1315A-1315N are optimized to execute fragment shader programs as provided for in the OpenGL API, which may be used to perform similar operations as a pixel shader program as provided for in the Direct 3D API.

Graphics processor 1310 additionally includes one or more memory management units (MMUs) 1320A-1320B, cache(s) 1325A-1325B, and circuit interconnect(s) 1330A-1330B. The one or more MMU(s) 1320A-1320B provide for virtual to physical address mapping for the graphics processor 1310, including for the vertex processor 1305 and/or fragment processor(s) 1315A-1315N, which may reference vertex or image/texture data stored in memory, in addition to vertex or image/texture data stored in the one or more cache(s) 1325A-1325B. In one embodiment the one or more MMU(s) 1320A-1320B may be synchronized with other MMUs within the system, including one or more MMUs associated with the one or more application processor(s) 1205, image processor 1215, and/or video processor 1220 of FIG. 12, such that each processor 1205-1220 can participate in a shared or unified virtual memory system. The one or more circuit interconnect(s) 1330A-1330B enable graphics processor 1310 to interface with other IP cores within the SoC, either via an internal bus of the SoC or via a direct connection, according to embodiments.

As shown FIG. 13B, graphics processor 1340 includes the one or more MMU(s) 1320A-1320B, caches 1325A-1325B, and circuit interconnects 1330A-1330B of the graphics processor 1310 of FIG. 13A. Graphics processor 1340 includes one or more shader core(s) 1355A-1355N (e.g., 1455A, 1355B, 1355C, 1355D, 1355E, 1355F, through 1355N−1, and 1355N), which provides for a unified shader core architecture in which a single core or type or core can execute all types of programmable shader code, including shader program code to implement vertex shaders, fragment shaders, and/or compute shaders. The exact number of shader cores present can vary among embodiments and implementations. Additionally, graphics processor 1340 includes an inter-core task manager 1345, which acts as a thread dispatcher to dispatch execution threads to one or more shader cores 1355A-1355N and a tiling unit 1358 to accelerate tiling operations for tile-based rendering, in which rendering operations for a scene are subdivided in image space, for example to exploit local spatial coherence within a scene or to optimize use of internal caches.

FIGS. 14A-14B illustrate additional exemplary graphics processor logic according to embodiments described herein. FIG. 14A illustrates a graphics core 1400 that may be included within the graphics processor 1210 of FIG. 12, and may be a unified shader core 1355A-1355N as in FIG. 13B. FIG. 14B illustrates a highly-parallel general-purpose graphics processing unit 1430 suitable for deployment on a multi-chip module.

As shown in FIG. 14A, the graphics core 1400 includes a shared instruction cache 1402, a texture unit 1418, and a cache/shared memory 1420 that are common to the execution resources within the graphics core 1400. The graphics core 1400 can include multiple slices 1401A-1401N or partition for each core, and a graphics processor can include multiple instances of the graphics core 1400. The slices 1401A-1401N can include support logic including a local instruction cache 1404A-1404N, a thread scheduler 1406A-1406N, a thread dispatcher 1408A-1408N, and a set of registers 1410A. To perform logic operations, the slices 1401A-1401N can include a set of additional function units (AFUs 1412A-1412N), floating-point units (FPU 1414A-1414N), integer arithmetic logic units (ALUs 1416-1416N), address computational units (ACU 1413A-1413N), double-precision floating-point units (DPFPU 1415A-1415N), and matrix processing units (MPU 1417A-1417N).

Some of the computational units operate at a specific precision. For example, the FPUs 1414A-1414N can perform single-precision (32-bit) and half-precision (16-bit) floating point operations, while the DPFPUs 1415A-1415N perform double precision (64-bit) floating point operations. The ALUs 1416A-1416N can perform variable precision integer operations at 8-bit, 16-bit, and 32-bit precision, and can be configured for mixed precision operations. The MPUs 1417A-1417N can also be configured for mixed precision matrix operations, including half-precision floating point and 8-bit integer operations. The MPUs 1417-1417N can perform a variety of matrix operations to accelerate machine learning application frameworks, including enabling support for accelerated general matrix to matrix multiplication (GEMM). The AFUs 1412A-1412N can perform additional logic operations not supported by the floating-point or integer units, including trigonometric operations (e.g., Sine, Cosine, etc.).

As shown in FIG. 14B, a general-purpose processing unit (GPGPU) 1430 can be configured to enable highly-parallel compute operations to be performed by an array of graphics processing units. Additionally, the GPGPU 1430 can be linked directly to other instances of the GPGPU to create a multi-GPU cluster to improve training speed for particularly deep neural networks. The GPGPU 1430 includes a host interface 1432 to enable a connection with a host processor. In one embodiment the host interface 1432 is a PCI Express interface. However, the host interface can also be a vendor specific communications interface or communications fabric. The GPGPU 1430 receives commands from the host processor and uses a global scheduler 1434 to distribute execution threads associated with those commands to a set of compute clusters 1436A-1436H. The compute clusters 1436A-1436H share a cache memory 1438. The cache memory 1438 can serve as a higher-level cache for cache memories within the compute clusters 1436A-1436H.

The GPGPU 1430 includes memory 1434A-1434B coupled with the compute clusters 1436A-1436H via a set of memory controllers 1442A-1442B. In various embodiments, the memory 1434A-1434B can include various types of memory devices including dynamic random access memory (DRAM) or graphics random access memory, such as synchronous graphics random access memory (SGRAM), including graphics double data rate (GDDR) memory.

In one embodiment the compute clusters 1436A-1436H each include a set of graphics cores, such as the graphics core 1400 of FIG. 14A, which can include multiple types of integer and floating point logic units that can perform computational operations at a range of precisions including suited for machine learning computations. For example and in one embodiment at least a subset of the floating point units in each of the compute clusters 1436A-1436H can be configured to perform 16-bit or 32-bit floating point operations, while a different subset of the floating point units can be configured to perform 64-bit floating point operations.

Multiple instances of the GPGPU 1430 can be configured to operate as a compute cluster. The communication mechanism used by the compute cluster for synchronization and data exchange varies across embodiments. In one embodiment the multiple instances of the GPGPU 1430 communicate over the host interface 1432. In one embodiment the GPGPU 1430 includes an I/O hub 1439 that couples the GPGPU 1430 with a GPU link 1440 that enables a direct connection to other instances of the GPGPU. In one embodiment the GPU link 1440 is coupled to a dedicated GPU-to-GPU bridge that enables communication and synchronization between multiple instances of the GPGPU 1430. In one embodiment the GPU link 1440 couples with a high speed interconnect to transmit and receive data to other GPGPUs or parallel processors. In one embodiment the multiple instances of the GPGPU 1430 are located in separate data processing systems and communicate via a network device that is accessible via the host interface 1432. In one embodiment the GPU link 1440 can be configured to enable a connection to a host processor in addition to or as an alternative to the host interface 1432.

While the illustrated configuration of the GPGPU 1430 can be configured to train neural networks, one embodiment provides alternate configuration of the GPGPU 1430 that can be configured for deployment within a high performance or low power inferencing platform. In an inferencing configuration the GPGPU 1430 includes fewer of the compute clusters 1436A-1436H relative to the training configuration. Additionally, the memory technology associated with the memory 1434A-1434B may differ between inferencing and training configurations, with higher bandwidth memory technologies devoted to training configurations. In one embodiment the inferencing configuration of the GPGPU 1430 can support inferencing specific instructions. For example, an inferencing configuration can provide support for one or more 8-bit integer dot product instructions, which are commonly used during inferencing operations for deployed neural networks.

A. Overview

Embodiments may be implemented within a virtual reality system such as that illustrated in FIG. 15A which includes a graphics system component 1580 and a head-mounted display (HMD) 1550. In one embodiment, the HMD 1550 comprises a right display 1551 on which images frames are rendered for viewing by the user's right eye and a left display 1552 on which image frames are rendered for viewing by the user's left eye. Separate graphics engines, 1556 and 1557, include graphics processing pipelines for rendering the right and left image frames, respectively, in response to the execution of a particular virtual reality application 1561. Each of the graphics engines 1556-1557 may comprise a separate graphics processing unit (GPU). Alternatively, the graphics engines 1556-1557 may include different sets of graphics execution resources within a single GPU or spread across multiple GPUs. For example, in a virtualized environment, a separate virtual GPU (vGPU) may be allocated to each display 1551-1552. Regardless of how the GPU resources are partitioned, the graphics engines 1556-1557 may implement any of the graphics processing techniques described herein.

In one embodiment, a user/eye tracking device 1553 integrated on the HMD 1550 includes sensors to detect the current orientation of the user's head and the direction of the user's gaze. For example, the orientation of the user's head may be captured using optical sensors and accelerometers while the current direction of the user's gaze may be captured with optical eye tracking devices such as cameras. As illustrated, the user/eye tracking device 1553 provide the user's current view 1560 to the graphics system 1580, which then adjust graphics processing accordingly (i.e., to ensure that the current image frames being rendered are from the current perspective of the user).

In one embodiment, the virtual reality application 1561 utilizes a graphics application programming interface (API) 1562 to implement features of the graphics engines 1556-1557 as described herein. For example, the graphics API 1562 may be provided with a virtual reality software development kit (SDK) 1563 which a developer may use to generate application program code for the virtual reality application 1561. For example, the virtual reality SDK 1563 may include a compiler (and/or other design tools) to generate object code for the virtual reality application 1561 which uses the API 1562 (e.g., by making calls to functions/commands included in the API). One or more of the techniques described herein may be implemented using the graphics API 1562, hardware within the graphics engines 1556-1557, and/or a combination thereof.

FIG. 15B illustrates the various stages of the two graphics pipelines for the right and left displays 1551-1552 in accordance with one embodiment. In particular, rasterization-based pipelines are illustrated including an input assembler (IA) 1521A-B which reads index and vertex data and a vertex shader (VS) 1522A-B from memory 1515. As mentioned, commands may be received by the IA 1521A-B via the graphics API 1562. The vertex shader 1522A-B performs shading operations on each vertex (e.g., transforming each vertex's 3D position in virtual space to the 2D coordinate at which it appears on the screen) and generates results in the form of primitives (e.g., triangles). A geometry shader (GS) 1523A-B takes a whole primitive as input, possibly with adjacency information. For example, when operating on triangles, the three vertices are the geometry shader's input. The geometry shader 1523A-B can then emit zero or more primitives, which are rasterized at a rasterization stage 1524A-B and the resulting fragments ultimately passed to a pixel shader (PS) 1525A-B, which performs shading operations on each of the individual pixels which are stored, frame by frame, within a frame buffer 1526A-B prior to being displayed on the HMD.

In one embodiment, a global illumination graphics processing architecture such as a ray tracing architecture may be employed. FIG. 15C, for example, illustrates an exemplary ray tracing-based graphics pipeline 1500 in which one or more pipeline stages 1501A-B to 1505A-B perform ray-tracing based rendering for the left and right displays 1551-1552. The illustrated stages include a ray generation module 1501A-B which generates rays for processing. For example, one embodiment performs breadth-first ray tracing per image tile, where a tile denotes a small fixed-size rectangular region. In one embodiment of a breadth-first implementation, one ray per pixel is generated for each iteration on the image tile. A ray traversal module 1502A-B traverses each ray against a bounding volume hierarchy (BVH) or other acceleration data structure. One or more intersection modules 1503A-B test the ray against one or more triangles or other primitives, and in the end, the traversal and intersection units must find the closest primitive that each ray intersects. One or more shader units 1504A-B then perform shading operations on the resulting pixels which are stored, frame by frame, within a frame buffer 1505A-B prior to being displayed on the HMD 1550.

B. Time Warping

Some embodiments may be employed in a VR system which uses time warping. Time warping is a technique used to improve performance in current virtual reality (VR) systems. According to this technique, each image frame is rendered in accordance with the current orientation of the user's head and/or eyes (i.e., as read from an eye tracking device and/or other sensors on the head mounted display (HMD) to detect the motion of the user's head). Just before displaying the next image frame, the sensor data is captured again and is used to transform the scene to fit the most recent sensor data (i.e., “warping” the current image frame). By taking advantage of the depth maps (i.e., Z Buffers) which have already been generated, time warping can move objects in 3D space with relatively low computational requirements.

One embodiment will be described with respect to FIG. 16 which illustrates a graphics processing engine 1300 communicatively coupled to a head-mounted display (HMD) 1350. A VR application 1310 is executed, generating graphics data and commands to be executed by the graphics processing engine 1300. The graphics processing engine 1300 may include one or more graphics processing units (GPUs) including a graphics pipeline to execute the graphics commands and render the image frames to be displayed on the HMD 1350 (e.g., such as the graphics pipelines described herein). For simplicity, only a single display 1617 is shown in FIG. 16, which may be the left and/or right display.

In operation, an image rendering module 1305 renders image frames to be displayed in the left and right displays 1617. In one embodiment, each image is rendered in accordance with a current orientation of the user's head and/or eyes, as provided by user/eye tracking module 1353 integrated on the HMD 1350. In particular, the HMD 1350 may include various sensors to track the current orientation of the user's head and cameras and associated circuitry/logic to track the current focus of the user's eyes. In a virtual reality implementation, this data is used to render left/right images from the correct perspective (i.e., based on the direction and focus of the user's current gaze).

While illustrated as a single component in FIG. 16 for simplicity, separate image rendering circuitry and logic may be used for the left and right image frames. Moreover, various other graphics pipeline stages are not illustrated to avoid obscuring the underlying principles including, for example, a vertex shader, geometry shader, and texture mapper. A ray tracing architecture employed in one embodiment may include a ray generation module, a ray traversal module, an intersection module, and a shading module. In any implementation, the rendering module 1605 renders images for the left and right displays 1617 based on the current orientation/gaze of the user.

In the illustrated embodiment, a first frame buffer 1616 is storing an image frame N−1, currently displayed within the left/right display 1617 of the HMD. The next image frame to be displayed (image frame N) is then rendered within a second frame buffer 1615. In one embodiment, the image rendering module 1605 uses the coordinate data provided by the user/eye tracking module 1553 to render the next frame within frame buffer 1615. At the time the next frame needs to be displayed within the left and/or right display 1617, time warp module 1620 transforms image frame N−1 or image frame N (if rendering of image frame N is complete) to fit the most recent sensor data provided by user/eye tracking module 1553. This transformation is performed by the time warp module 1620 using the previously-generated depth maps stored in the processing engine's Z-buffers 1618. The transformation moves objects in 3D space with relatively small computational requirements, resulting in a more recently completed product without the need to re-render the scene. Thus, in most cases, it should be substantially similar to the image frame which would have been rendered if rendering had occurred more quickly.

Time warping is a technique used to improve performance in current virtual reality (VR) systems. According to this technique, each image frame is rendered in accordance with the current orientation of the user's head and/or eyes (i.e., as read from an eye tracking device and/or other sensors on the head mounted display (HMD) to detect the motion of the user's head). Just before displaying the next image frame, the sensor data is captured again and is used to transform the scene to fit the most recent sensor data (i.e., “warping” the current image frame). By taking advantage of the depth maps (i.e., Z Buffers) which have already been generated, time warping can move objects in 3D space with relatively low computational requirements.

One embodiment uses time warping techniques to warp a portion of a previously-rendered image frame and combining the results with the partially rendered current frame. For example, a currently-rendered frame may have a region of data which has been lost or corrupted due to transmission errors or other data processing errors. Similarly, the graphics rendering pipeline may have only been able to render a portion of the next image frame when it is time to display the image frame (e.g., given a required or specified frame rate for the VR system). In one embodiment, when a portion of a current image frame has not been rendered and/or has been lost/corrupted, the corresponding portion is read from the prior image frame which is then warped in accordance with the current sensor data. The warped portion of the prior image frame is then combined with the correctly-rendered portion of the current image frame and displayed on the VR display.

One embodiment will be described with respect to FIG. 17 which illustrates a graphics processing engine 1700 communicatively coupled to a head-mounted display (HMD) 1750. A VR application 1710 is executed, generating graphics data and commands to be executed by the graphics processing engine 1700. The graphics processing engine 1700 may include one or more graphics processing units (GPUs) including a graphics pipeline to execute the graphics commands and render the image frames to be displayed on the HMD 1750. In particular, the HMD may include a left display for displaying images for the user's left eye and a right display for displaying images for the user's right eye. For simplicity, only a single display 1740 is shown in FIG. 17, which may be the left or right display.

In operation, an image rendering module 1705 renders image frames to be displayed in the left and right displays 1740. In one embodiment, each image is rendered in accordance with a current orientation of the user's head and/or eyes, as provided by user/eye tracking module 1730 integrated on the HMD 1750. In particular, the HMD may include various sensors to track the current orientation of the user's head and cameras and associated circuitry/logic to track the current focus of the user's eyes. In a virtual reality implementation, this data is used to render left/right images from the correct perspective (i.e., based on the direction and focus of the user's current gaze).

While illustrated as a single component in FIG. 17 for simplicity, separate image rendering circuitry and logic may be used for the left and right image frames. Moreover, various other graphics pipeline stages are not illustrated to avoid obscuring the underlying principles including, for example, a vertex shader, geometry shader, and texture mapper. A ray tracing architecture employed in one embodiment may include a ray generation module, a ray traversal module, an intersection module, and a shading module. In any implementation, the rendering module 1705 renders images for the left and right displays 1740 based on the current orientation/gaze of the user.

In the illustrated embodiment, a first frame buffer 1716 is storing an image frame N−1, currently displayed within the left/right display 1740 of the HMD 1750. The next image frame to be displayed (image frame N) is being rendered within a second frame buffer 1706. In particular, a first portion 1715 of the image frame has been correctly rendered while a second portion 1717 is has not yet been rendered. As mentioned, portion 1717 may be corrupted due to a communication error or other form of error. Alternatively, image rendering module 1705 may not have rendered the full image quickly enough to meet the frame rate required by the HMD 1750.

In either case, in one embodiment, time warp module 1720 selects a corresponding portion 1716A of the image frame N−1 in frame buffer 1716, performs a time warp operation on the contents of the portion 1716A to generate a warped portion 1716B, which is then combined with the rendered portion of the image 1715 to arrive at the final image on the right/left display 1740. In particular, the time warp module 1720 reads the sensor data from the user/eye tracking module 1730 to transform the portion of the prior image 1716A to fit the most recent sensor data. This transformation is performed by the time warp module using the previously-generated depth maps stored in the processing engine's Z-buffers 1718. The transformation moves objects in 3D space with relatively small computational requirements, resulting in a more recently completed product without the need to re-render the scene. Thus, in most cases, it should be substantially similar to the portion 1717 which would have been generated if rendering had occurred correctly.

As illustrated in FIG. 18, rather than transferring the warped portion 1816B directly to the left/right display 1840, one embodiment of the time warp module 1820 copies the image portion to the frame buffer 1806 from which the final image (2215+1816B) is read to the display 1840. The underlying principles are not limited to any particular technique for combining the warped portion of the prior image frame 1816B with the portion of the rendered frame 1815.

A method in accordance with one embodiment is illustrated in FIG. 19. The method may be implemented within the context of the system architectures described above, but is not limited to any particular set of processing resources.

At 1900, image frame N−1 is rendered for the left/right display. At 1901, rendering begins for image frame N and at 1902, it is time to display image frame N. If image frame N is incomplete, determined at 1903, then at 2804 the incomplete region in image frame N and the corresponding region in image frame N−1 is identified. At 1905, the corresponding region in image frame N−1 is warped based on current coordinates provided by the HMD sensors and the warped results are combined with the completed region from frame N. The resulting image is displayed at 1906.

Time warp algorithms today render a much larger image than required. Time warp then samples this image based on the user's actual head position when each scan line is read out. This leads to scanlines being “sheared” which necessitates the larger draw area. One embodiment predicts which time warp will happen based on head motion, and concentrates rendering efforts into the predicted region of the frame. One embodiment renders the warped image with a ray tracer (adjusting the view position and direction per scan line). In one embodiment, a rasterizer uses a sheared projection matrix. Motion data, acceleration data, and data from other sensors may be exploited to predict the position and orientation of the user's head and eyes. In short, being able to predict the shearing effect that is going to happen during resampling means a smaller overdraw region can be used, and thus faster/cheaper rendering.

The basic rationale for the time warp algorithm is that a good VR experience requires extremely low latency between head motion and display of the pixels. In a head mounted display (HMD), however, frame buffers are not filled instantaneously, but scan line by scan line; thus, during fast head motion the actual head direction by the time a given scan line is read out may no longer correspond to the camera direction used when rendering the frame. The “time warp” algorithm accounts for that fact by rendering a single, larger frame at the beginning of each frame, sending that to the VR device, and have the HMD device sample this large, readily-rendered frame buffer, for each pixel (or scanline), using the respective head orientation at the time the scan line is read out. In practice, during fast head motion this means that the actual pixels (re-)sampled from the original frame buffer are “sheared” inside that frame buffer. In particular, to make sure that all sheared samples fall to valid pixels in that original image, the original image has to be significantly larger than the final number of samples, meaning that the original image has to spend time, power, and effort to compute pixels that will eventually never be accessed by any sample.

If, however, the likely sheared sample pattern that the HMD will actually access can be predicted, some of this “overdraw” can be avoided for faster and/or cheaper rendering. In one embodiment a sheared image is directly rendered, either using a sheared projection matrix (for a rasterizer) or using a properly sheared ray generation code (for a ray tracer). In another embodiment, a full frame is rendered (with a regular view matrix and full overdraw), but rendering quality is adjusted in the region of interest indicated by the projected shear. For example, in the extreme case, any pixel outside of the sheared region might get stenciled out completely; in a less extreme setting these pixels would still get rendered but at lower quality (lower render resolution, lower anti-aliasing settings, cheaper shader, etc).

FIG. 20 illustrates one embodiment in which a VR application is executed by a graphics processing engine 2000 equipped with a left/right image rendering pipeline 2005 which outputs rendered images into one or more render buffers 2006. As illustrated in FIG. 20, in the first of these embodiments (rendering a sheared input image), prediction logic 2021 generates a sheared projection matrix 2035 based on predicted motion of the user's eyes. The shearing matrix 2035 is passed to the HMD 2050 which includes shear compensation logic 2040 that accounts for this pre-shear by subtracting it from the actual shear required for the time warp algorithm 2020. The results are then displayed on the left/right displays 2045 of the HMD. In the second embodiment (changing render quality in the sheared region) this is not required.

For the method to work all is required is the proper motion and acceleration vectors to determine the camera positions at the time the first and last scan lines will be read out by the HMD. In the case of using a single sheared matrix we can then compute a shared projection matrix (using a single fixed camera origin) that covers this entire time interval; in the case of using a ray tracer we can actually compute both eye position and camera orientation for each scan line separately, even having a different camera origin per scan line.

Current augmented reality (AR) systems render separate image streams for a “real” image and one or more “virtual” images. The real image may be captured via a camera or optical lens included on a head mounted display (HMD) while the virtual images are rendered by a 3D graphics pipeline and combined with the real image to create the “augmented” reality.

As illustrated in FIG. 21, the different sets of execution resources 2101A-2106A, 2101B-2106B may be allocated at various stages of the graphics pipeline including the input assembler (IA) 2101A-B which reads index and vertex data and a vertex shader (VS) 2102A-B from memory; the vertex shader stage 2102A-B which performs shading operations on each vertex (e.g., transforming each vertex's 3D position in virtual space to the 2D coordinate at which it appears on the screen) and generates results in the form of primitives (e.g., triangles); the geometry shader (GS) stage 2103A-B which takes a whole primitive as input, possibly with adjacency information (e.g., three vertices for each triangle); a rasterization stage 2104A-B which rasterizes primitives provided by the geometry shader; and a pixel shader (PS) stage 2105A-B, which performs shading operations on each of the individual pixels which are stored, frame by frame, within a frame buffer 2106A-B prior to being displayed on the HMD 2150. For example, in one embodiment, different number of execution units may be allocated to the right and left displays 2151-2152 for performing rasterization and pixel shading operations (e.g., allocating more execution units to the dominant eye).

While a rasterization-based pipeline is illustrated in FIG. 21, the underlying principles are not so limited. For example, FIG. 22 illustrates one embodiment implemented within a ray tracing-based pipeline with various pipeline stages 2201A-2205A, 2201A-2205A in which resources may be allocated in accordance with the user's dominant/non-dominant eye or LE/HE. The illustrated stages include a ray generation module 2201A-B which generates rays for further processing. For example, one embodiment performs breadth-first ray tracing per image tile, where a tile denotes a small fixed-size rectangular region. In one embodiment of a breadth-first implementation, one ray per pixel is generated for each iteration on the image tile. A ray traversal module 2202A-B traverses each ray against a bounding volume hierarchy (BVH) or other acceleration data structure. One or more intersection modules 2203A-B test the ray against one or more triangles or other primitives, and in the end, the traversal and intersection units must find the closest primitive that each ray intersects. One or more shader units 2204A-B then perform shading operations on the resulting pixels which are stored, frame by frame, within a frame buffer 2205A-B prior to being displayed on the HMD 2150. Various different types of hardware and software may be allocated at each stage of the pipeline in accordance with the user's vision (e.g., a different number of execution units for performing shading operations).

Policies and Architecture to Dynamically Offload VR Processing to HMD Based on External Cues

As described above, various VR operations (e.g., barrel distortion (BD) correction, asynchronous time warp (ATW), chromatic aberration correction (CAC), etc.) can lead to frame drops and latencies which may lead to a poor user experience. One way to address is by offloading all or portions of these operations from the host computer (e.g. a personal computer, gaming console, or other external graphics processing apparatus) to one or more graphics engines incorporated into a wearable graphics processing apparatus, such as a head mounted display (HMD). Offloading these functions provides relief to the host graphics processor, increasing the likelihood that frames are rendered in time (e.g., completed before the next vsync). Avoiding frame drops and latencies in the VR pipeline improves the user experience. While such offloading can provide meaningful graphics relief, in some dynamic situations, an offloaded setup may perform worse than a non-offloaded setup. For example, the HMD could start overheating, performance throttling, running low on battery (e.g. wireless VR) etc. while operating for extended periods. In such situations, performance may be improved using an optimized architecture which can dynamically offload/on-load processing across host and HMD, based on various cues from the overall system.

FIG. 23 illustrates one embodiment of an architecture for performing offloading of processing to a head mounted display. As shown in FIG. 23, a host system, such as graphics system 1580 described above, can perform graphics processing and output the results to a head mounted display 2300 which includes a right display 2302 and a left display 2304. Additionally, HMD 2300 can further include its own graphics engines 2306, 2308. Each of the graphics engines 2306, 2308 may comprise a separate graphics processing unit (GPU). Alternatively, the graphics engines 2306, 2308 may include different sets of graphics execution resources within a single GPU or spread across multiple GPUs. For example, in a virtualized environment, a separate virtual GPU (vGPU) may be allocated to each display 2302, 2304. Regardless of how the GPU resources are partitioned, the graphics engines 2306, 2308 may implement any of the graphics processing techniques described herein. Additionally, graphics engines 2306, 2308 on HMD 2300 can provide additional processing resources to the graphics system, enabling the graphics system to dynamically offload/onload 2310 graphics processing as needed based on one or more external cues, such as current performance and/or graphics system or HMD status.

In some embodiments, HMD 2300 can communicate its VR processing capabilities (e.g., details of graphics engines 2306, 2308) to the graphics system when the HMD is connected. The graphics system can select an initial set of processing that should be enabled on the HMD. The graphics system can then dynamically turn on/off processing features during the course of operation, causing processing to be shifted from the graphics system's graphics engines to the HMD's graphics engines, or causing processing to be shifted back to the graphics system. The decision to dynamically offload or onload graphics processing can be based on feedback or other cues from the host system, network, or through asynchronous alerts received from the HMD. In some embodiments, policies may be used to define how processing is to be allocated in response to various cues. This is discussed further with respect to FIG. 24.

FIG. 24 illustrates one embodiment of an architecture for performing offloading of processing to a head mounted display. As shown in FIG. 24, host 2402 and HMD 2404 may each include monitors and controllers which are used to manage the distribution of processing across available resources according to one or more policies. In the example of FIG. 24, the host and the HMD each include a VR processor 2410, 2428 and state controller 2408, 2426. Each VR Processor module is the logical entity that performs the graphics processing operations, and may correspond to graphics engines 3006, 3008. VR processors 2410, 2428 may include one or more graphics processing units. Each state controller 2408, 2426 enables/disables operations done in the VR Processor. Additionally, an offload controller module 2414, 2424 negotiates offload capabilities and enables/disables HMD side processing based on inputs from other logic, as further discussed below.

The offload controllers may enable/disable processing by each VR processor using one or more policies and feedback received from different monitors on the host and HMD. For example, when HMD's battery level reaches a low threshold a battery monitor 2420 can send an alert to alerts receiver 2416. The alerts receiver can compare the battery level to a battery policy, and instruct offload controller 2414 to disable post processing on the HMD to save power, and enable post processing by the host. Offload controller 2414 can instruct state controller 2408 to enable post processing features on VR processor 2410, and can further instruct offload controller 2424 to disable these features on HMD 2404.

In some embodiments, performance may also degrade as the HMD heats up, such as during extended use. A thermal budget monitor 2418 can monitor the temperature of the HMD and/or specific components of the HMD, such as the VR processor 2428. When the HMD, or a component thereof, reaches its thermal budget, the thermal monitor 2418 can send an alert to the alerts received 2416. In some embodiments, the thermal budget may be a value specified in a thermal policy. The alerts receiver can instruct offload controller 2414 to disable post processing on the HMD to reduce the heat produced on the HMD, and enable post processing by the host. Offload controller 2414 can instruct state controller 2408 to enable post processing features on VR processor 2410, and can further instruct offload controller 2424 to disable these features on HMD 2404.

In some embodiments, a transmitter module 2412 and receiver module 2430 can monitor transport delays. As shown in FIG. 24, the host 2402 and HMD 2404 may be connected through a wired connection or a wireless connection. When the transmitter module detects meaningful and persistent transport (e.g. WiFi, WiGig, etc.) delays, the offload controller 2414 can enable the HMD to perform operations such as time warp processing. The offload controller 2414 can change the transmitted data format as necessary, to enable the HMD to perform time warp processing. This may include sending undistorted frames (e.g., to allow the HMD can perform distortion correction), sensor metadata used by the frames (e.g., to allow the HMD to synthesize frames) etc. Doing so allows the HMD to synthesize frames based on the last frame received rather than waiting for the host to synthesize a new frame and rely on the transport to deliver it. Similarly, if the receive module 2430 detects transport delays, the receiver module 2430 may send an alert to alerts receiver 2416 and offload controller 2414 may similarly offload processing and/or reformat transmissions.

In some embodiments, a GPU monitor 2406 can monitor VR processor 2410 load. If the host GPU monitor 2406 detects an increasing load that could compromise render time, it alerts the offload controller 2414 to offload at least some processing operations to the HMD. The VR processor could become overloaded for various reasons, such as the host reaching its power budget limit and the OS throttling the GPU frequency. The conditions that qualify as overload may be defined in a GPU policy. Such overload may also happen if the host is running a complex game or application that takes longer to render each frame. The offload controller 2414 may then enable VR processing on the HMD, relieving the host VR processor 2410 of some work and letting the HMD VR processor 2428 to process the backlog. The offload controller may disable the HMD processing once the GPU is capable of running the workload again. Similarly, GPU monitor 2422 may monitor the processing load of VR processor 2428 and, like the host processor, if the HMD processor is becoming overloaded. In various embodiments, a policy may define conditions under which the VR processor is overloaded, such as a number of backlogged operations, an average processing time per instruction, or other metric. In some embodiments, policies may be defined for each processor or core in the host and/or HMD.

In some embodiments, transmitter module 2412 may monitor a transmission queue to determine if there is a backlog above a threshold value. If the transmitter module 2412 determines that a backlog exists, the offload controller can enable processing on the HMD, allowing it to time warp the last received frame as mentioned. Additionally, the HMD's receiver module can monitor a receiver queue for backlog by the HMD. If a backlog is detected, an alert can be sent by receiver module 2430 to the alerts receiver 2416. The offload controller 2414 can enable processing on the host until the HMD has reduced its backlog.

FIG. 25 illustrates a method in accordance with one embodiment. As shown in FIG. 25, at 2500 data identifying available VR processing operations are sent from the HMD to the host. At 2502, the host can determine one or more of the VR operations to be performed by the HMD. At 2504, the host can activate the one or more VR operations on the HMD. At 2506, the HMD can perform the one or more VR operations. At 2508, the HMD can monitor performance characteristics of the HMD. At 2510, one or more performance monitors installed on the HMD may send performance characteristics to the host. At 2512, the host can compare the HMD performance characteristics to one or more offload policies. At 2514, the host can dynamically onload at least one of the one or more VR operations from the HMD. At 2516, the host can deactivate the at least one VR operation on the HMD.

FIG. 26 illustrates a method in accordance with one embodiment. As shown in FIG. 26, at 2600 data identifying available VR processing operations are sent from the HMD to the host. At 2602, the host can determine one or more of the VR operations to be performed by the HMD. At 2604, the host can execute one or more VR operations. At 2606, the host can monitor performance characteristics of the host. At 2608, the host can compare the HMD performance characteristics to one or more offload policies. At 2610, the host can dynamically offload at least one of the one or more VR operations to the HMD. At 2612, the host can activate the at least one VR operation on the HMD. At 2614, the HMD can execute the one or more VR operations.

1. A wearable graphics processing apparatus comprising: one or more displays to display visual images; at least one performance monitor coupled to at least one component of the wearable graphics processing apparatus, the at least one performance monitor to monitor performance of the at least one component and to generate an alert based on the performance of the at least one component; a communications interface to receive frame data of a virtual reality scene from an external graphics processing apparatus; a processor to process the frame data to generate the visual images on the one or more displays; and a controller to receive the alert based on the performance of the at least one component and to transmit the alert over the communications interface to the external graphics processing apparatus to offload additional processing of at least some of the frame data from the processor to the external graphics processing apparatus.

2. The wearable graphics processing apparatus of example 1, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

3. The wearable graphics processing apparatus of example 1, wherein the at least one performance monitor is a battery monitor coupled to a battery of the wearable display apparatus, the batter monitor to determine a current battery level and wherein the alert is sent when the current battery level is below a threshold.

4. The wearable graphics processing apparatus of example 1, wherein the at least one performance monitor is a thermal monitor coupled to the processor, the thermal monitor to measure a current heat level of the processor and send the alert when the current heat level exceeds a threshold.

5. The wearable graphics processing apparatus of example 1, wherein the at least one performance monitor is a transport monitor coupled to a receive queue, the transport monitor to determine a size of the receive queue and send the alert when the size exceeds a threshold value.

6. The wearable graphics processing apparatus of example 1, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

7. The wearable graphics processing apparatus of example 1, wherein the communication interface comprises a wireless communication interface to provide a wireless communication channel with the external graphics processing apparatus.

8. The wearable graphics processing apparatus of example 1, wherein the frame data comprises data for image frames rendered by the external graphics processing apparatus.

9. The wearable graphics processing apparatus of example 1, wherein processing of the frame data includes time warp processing.

10. The wearable graphics processing apparatus of example 9, further comprising: one or more sensors to track a current orientation of a user's view and to provide data indicating the view to the processor, the processor to perform time warp processing of the frame data based on the data indicating the view.

11. An apparatus comprising: a communications interface to provide frame data of a virtual reality scene to a wearable graphics processing apparatus; at least one performance monitor coupled to at least one component of the apparatus the at least one performance monitor to monitor performance of the at least one component and to send an alert based on the performance of the at least one component; a processor to process the frame data into processed frame data; a controller to receive the alert based on the performance of the at least one component and to offload processing of the frame data from the processor to the wearable graphics processing apparatus for processing; and a display to show the processed frame data of the virtual reality scene.

12. The apparatus as in example 11, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

13. The apparatus as in example 11, wherein the at least one performance monitor is a transport monitor coupled to a transmit queue, the transport monitor to determine a size of the transmit queue and send the alert when the size exceeds a threshold value.

14. The apparatus as in example 11, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

15. The apparatus as in example 11, wherein processing of the frame data includes time warp processing.

16. A system comprising: a host computer including a host processor, a host offload controller, and an alerts receiver; and a head mounted display (HMD) including an HMD processor and at least one HMD performance monitor, the HMD to: send, to the host computer, data identifying virtual reality (VR) processing operations executable by the HMD processor; receive an activation instruction from the host offload controller to activate the VR processing operations on the HMD processor; receive frame data from the host computer; execute the VR processing operations on the frame data; monitor HMD performance characteristics by the HMD performance monitor; send an alert to the alerts receiver based on the HMD performance characteristics; and receive a deactivate instruction from the host offload controller to deactivate the VR processing operations on the HMD processor.

17. The system as in example 16, wherein the HMD further comprises an HMD offload controller, and wherein the host computer further comprises a host performance monitor, the host to: execute the VR processing operations by the host processor; monitor host performance characteristics by the host performance monitor; send a second alert to the alerts receiver based on the host performance characteristics; and dynamically offload the VR processing operations by sending a second activation instruction to the HMD offload controller.

18. The system as in example 16, wherein the at least one HMD performance monitor is a processor monitor to determine that the HMD processor is overloaded.

19. The system as in example 16, wherein the at least one HMD performance monitor is a battery monitor coupled to a battery of the head mounted display, the batter monitor to determine a current battery level and wherein the alert is sent when the current battery level is below a threshold.

20. The system as in example 16, wherein the at least one HMD performance monitor is a thermal monitor coupled to the processor, the thermal monitor to measure a current heat level of the processor and send the alert when the current heat level exceeds a threshold.

21 The system as in example 16, wherein the at least one HMD performance monitor is a transport monitor coupled to a receive queue, the transport monitor to determine a size of the receive queue and send the alert when the size exceeds a threshold value.

22. The system as in example 17, wherein the host performance monitor is a processor monitor to determine that the host processor is overloaded.

23. The system as in example 17, wherein the host performance monitor is a transport monitor coupled to a transmit queue, the transport monitor to determine a size of the transmit queue and send the alert when the size exceeds a threshold value.

24. A method comprising: receiving, by a wearable graphics processing apparatus, frame data of a virtual reality scene from an external graphics processing apparatus; processing, by at least one processor of the wearable graphics processing apparatus, the frame data to generate visual images on one or more displays of the wearable graphics processing apparatus; monitoring, by a performance monitor, performance of at least one component of the wearable graphics processing apparatus; generating, by the performance monitor, an alert based on the performance of the at least one component; and transmitting the alert over a communications interface to the external graphics processing apparatus to offload additional processing of at least some of the frame data to the external graphics processing apparatus.

25. The method as in example 24, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

26. The method as in example 24, wherein the at least one performance monitor is a battery monitor coupled to a battery of the wearable graphics processing apparatus, the batter monitor to determine a current battery level and wherein the alert is sent when the current battery level is below a threshold.

27. The method as in example 24, wherein the at least one performance monitor is a thermal monitor coupled to the processor, the thermal monitor to measure a current heat level of the processor and send the alert when the current heat level exceeds a threshold.

28. The method as in example 24, wherein the at least one performance monitor is a transport monitor coupled to a receive queue, the transport monitor to determine a size of the receive queue and send the alert when the size exceeds a threshold value.

29. The method as in example 24, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

30. The method as in example 24, wherein the communication interface comprises a wireless communication interface to provide a wireless communication channel with the external graphics processing apparatus.

31. The method of example 24, wherein the frame data comprises data for image frames rendered by the external graphics processing apparatus.

32. The method of example 24, wherein processing of the frame data includes time warp processing.

33. The method of example 32, wherein the wearable graphics processing apparatus comprises one or more sensors to track a current orientation of a user's view and to provide data indicating the view to the processor, the processor to perform time warp processing of the frame data based on the data indicating the view.

34. A method comprising: processing, by a graphics processing apparatus, frame data of a virtual reality scene into processed frame data; monitoring, by a performance monitor, performance of at least one component of the graphics processing apparatus; sending, by the performance monitor, an alert based on the performance of the at least one component to a controller on the graphics processing apparatus; offloading, by the controller, processing of the frame data from the graphics processing apparatus to a wearable graphics processing apparatus, based on the alert; and providing, by the graphics processing apparatus, the frame data or the processed frame data to the wearable graphics processing apparatus for processing.

35. The method as in example 34, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

36. The method as in example 34, wherein the at least one performance monitor is a transport monitor coupled to a transmit queue, the transport monitor to determine a size of the transmit queue and send the alert when the size exceeds a threshold value.

37. The method as in example 34, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

38. The method as in example 34, wherein processing of the frame data includes time warp processing.

39. A non-transitory computer readable storage medium including instructions stored thereon which, when executed by a processor, cause the processor to: receive, by a wearable graphics processing apparatus, frame data of a virtual reality scene from an external graphics processing apparatus; process, by at least one processor of the wearable graphics processing apparatus, the frame data to generate visual images on one or more displays of the wearable graphics processing apparatus; monitor, by a performance monitor, performance of at least one component of the wearable graphics processing apparatus; generate, by the performance monitor, an alert based on the performance of the at least one component; and transmit the alert over a communications interface to the external graphics processing apparatus to offload additional processing of at least some of the frame data to the external graphics processing apparatus.

40. The non-transitory computer readable storage medium as in example 39, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

41. The non-transitory computer readable storage medium as in example 39, wherein the at least one performance monitor is a battery monitor coupled to a battery of the wearable graphics processing apparatus, the batter monitor to determine a current battery level and wherein the alert is sent when the current battery level is below a threshold.

42. The non-transitory computer readable storage medium as in example 39, wherein the at least one performance monitor is a thermal monitor coupled to the processor, the thermal monitor to measure a current heat level of the processor and send the alert when the current heat level exceeds a threshold.

43. The non-transitory computer readable storage medium as in example 39, wherein the at least one performance monitor is a transport monitor coupled to a receive queue, the transport monitor to determine a size of the receive queue and send the alert when the size exceeds a threshold value.

44. The non-transitory computer readable storage medium as in example 39, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

45. The non-transitory computer readable storage medium as in example 39, wherein the communication interface comprises a wireless communication interface to provide a wireless communication channel with the external graphics processing apparatus.

46. The non-transitory computer readable storage medium of example 39, wherein the frame data comprises data for image frames rendered by the graphics processing apparatus.

47. The non-transitory computer readable storage medium of example 39, wherein processing of the frame data includes time warp processing.

48. The non-transitory computer readable storage medium of example 47, wherein the wearable graphics processing apparatus comprises one or more sensors to track a current orientation of a user's view and to provide data indicating the view to the processor, the processor to perform time warp processing of the frame data based on the data indicating the view.

49. A non-transitory computer readable storage medium including instructions stored thereon which, when executed by a processor, cause the processor to: process frame data of a virtual reality scene into processed frame data; cause a performance monitor to monitor performance of at least one component of a computer; sending an alert based on the performance of the at least one component to a controller on the computer; offloading, by the controller, processing of the frame data from the computer to a wearable graphics processing apparatus, based on the alert; and providing, by the computer, the frame data or the processed frame data to the wearable graphics processing apparatus for processing.

50. The non-transitory computer readable storage medium as in example 49, wherein the at least one performance monitor is a processor monitor to determine that the processor is overloaded.

51. The non-transitory computer readable storage medium as in example 49, wherein the at least one performance monitor is a transport monitor coupled to a transmit queue, the transport monitor to determine a size of the transmit queue and send the alert when the size exceeds a threshold value.

52. The non-transitory computer readable storage medium as in example 49, wherein the at least one performance monitor includes a performance policy that defines an offload condition, and wherein the performance monitor sends the alert when the offload condition is met.

53. The non-transitory computer readable storage medium as in example 49, wherein processing of the frame data includes time warp processing.

The terms “module,” “logic,” and “unit” used in the present application, may refer to a circuit for performing the function specified. In some embodiments, the function specified may be performed by a circuit in combination with software such as by software executed by a general purpose processor.

Embodiments may include various steps, which have been described above. The steps may be embodied in machine-executable instructions which may be used to cause a general-purpose or special-purpose processor to perform the steps. Alternatively, these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

As described herein, instructions may refer to specific configurations of hardware such as application specific integrated circuits (ASICs) configured to perform certain operations or having a predetermined functionality or software instructions stored in memory embodied in a non-transitory computer readable medium. Thus, the techniques shown in the figures can be implemented using code and data stored and executed on one or more electronic devices (e.g., an end station, a network element, etc.). Such electronic devices store and communicate (internally and/or with other electronic devices over a network) code and data using computer machine-readable media, such as non-transitory computer machine-readable storage media (e.g., magnetic disks; optical disks; random access memory; read only memory; flash memory devices; phase-change memory) and transitory computer machine-readable communication media (e.g., electrical, optical, acoustical or other form of propagated signals—such as carrier waves, infrared signals, digital signals, etc.).

In addition, such electronic devices typically include a set of one or more processors coupled to one or more other components, such as one or more storage devices (non-transitory machine-readable storage media), user input/output devices (e.g., a keyboard, a touchscreen, and/or a display), and network connections. The coupling of the set of processors and other components is typically through one or more busses and bridges (also termed as bus controllers). The storage device and signals carrying the network traffic respectively represent one or more machine-readable storage media and machine-readable communication media. Thus, the storage device of a given electronic device typically stores code and/or data for execution on the set of one or more processors of that electronic device. Of course, one or more parts of an embodiment may be implemented using different combinations of software, firmware, and/or hardware. Throughout this detailed description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without some of these specific details. In certain instances, well known structures and functions were not described in elaborate detail in order to avoid obscuring the subject matter of various embodiments. Accordingly, the scope and spirit of embodiments should be judged in terms of the claims which follow. 

1. (canceled)
 2. A wearable graphics processing apparatus comprising: one or more displays to display visual images; at least one monitor coupled to at least one component of the wearable graphics processing apparatus, the monitor to monitor a power status of the wearable graphics processing apparatus; a communications interface to receive frame data of a virtual reality scene from an external graphics processing apparatus; and a processor to process the received frame data to generate visual images on the one or more displays; and wherein the processor is disabled from processing the frame data responsive to the power status of the wearable graphics processing apparatus.
 3. The wearable graphics processing apparatus of claim 2, wherein the at least one monitor is a battery monitor coupled to a battery, and wherein the power status indicates that a battery level of the wearable graphics processing apparatus reaches a threshold.
 4. The wearable graphics processing apparatus of claim 2, wherein the at least one monitor is a thermal monitor, and wherein the power status indicates that a temperature of the at least one component of the wearable graphics processing apparatus reaches its thermal budget.
 5. The wearable graphics processing apparatus of claim 4, wherein the thermal monitor is coupled to the processor, and wherein the thermal monitor is to measure a current heat level of the processor and the power status is that the current heat level exceeds a threshold.
 6. The wearable graphics processing apparatus of claim 2, wherein the frame data comprises data for image frames rendered by the external graphics processing apparatus.
 7. The wearable graphics processing apparatus of claim 2, wherein processing of the frame data includes time warp processing.
 8. The wearable graphics processing apparatus of claim 2, wherein processing of the frame data includes chromatic aberration correction.
 9. The wearable graphics processing apparatus of claim 2, wherein processing of the frame data includes barrel distortion (BD) correction.
 10. A method comprising: receiving, by a wearable graphics processing apparatus, frame data of a virtual reality scene from an external graphics processing apparatus; processing, by a processor of the wearable graphics processing apparatus, the received frame data to generate visual images on one or more displays of the wearable graphics processing apparatus; monitoring, by a monitor, a power status of the wearable graphics processing apparatus; and disabling the processor from processing the frame data responsive to the power status of the wearable graphics processing apparatus.
 11. The method of claim 10, wherein the monitor is a battery monitor coupled to a battery, and wherein the power status indicates that a battery level of the wearable graphics processing apparatus reaches a threshold.
 12. The method of claim 10, wherein the monitor is a thermal monitor, and wherein the power status indicates that a temperature of a component of the wearable graphics processing apparatus reaches its thermal budget.
 13. The method of claim 12, wherein the thermal monitor is coupled to the processor, and wherein the thermal monitor is to measure a current heat level of the processor and the power status is that the current heat level exceeds a threshold.
 14. The method of claim 10, wherein the frame data comprises data for image frames rendered by the external graphics processing apparatus.
 15. The method of claim 10, wherein processing of the frame data includes time warp processing.
 16. The method of claim 10, wherein processing of the frame data includes chromatic aberration correction.
 17. The method of claim 10, wherein processing of the frame data includes barrel distortion (BD) correction.
 18. A non-transitory machine-readable storage medium having program code stored thereon which, when executed by a machine, is capable of causing the machine to perform: receiving, by a wearable graphics processing apparatus, frame data of a virtual reality scene from an external graphics processing apparatus; processing, by a processor of the wearable graphics processing apparatus, the received frame data to generate visual images on one or more displays of the wearable graphics processing apparatus; monitoring, by a monitor, a power status of the wearable graphics processing apparatus; and disabling the processor from processing the frame data responsive to the power status of the wearable graphics processing apparatus.
 19. The non-transitory machine-readable storage medium of claim 18, wherein monitor is a battery monitor coupled to a battery, and wherein the power status indicates that a battery level of the wearable graphics processing apparatus reaches a threshold.
 20. The non-transitory machine-readable storage medium of claim 18, wherein the monitor is a thermal monitor, and wherein the power status indicates that a temperature of a component of the wearable graphics processing apparatus reaches its thermal budget.
 21. The non-transitory machine-readable storage medium of claim 18, wherein the frame data comprises data for image frames rendered by the external graphics processing apparatus. 